SBS2003 & Safenet VPN

-Have you tried disabling the Windows firewall, or any other software firewall, on the computer you are trying to connect to?
-Can you ping the computer you are trying to connect to?
-Is the share on the SBS, or are you connecting to a share on another computer? if the latter do you have multiple network adapters on the SBS, they may need to be configured to route the incoming traffic.

Though it is not likely the problem, the servers FQDN (Fully Qualified Domain Name) would be bnserver.bn.local, rather than bnserver@
You may have a DNS lookup problem, but regardless you should be able to connect using \\10.30.1.200\common_files   There is another problem here.

For one, your remote VPN clients need to be an a different subnet.  Also, you need to enable WINS server on sbs server and set up an LMHOSTS file on each of the clients in order for them to see the network shares.

i have been told the problem lies within the dns suffix.

at work there are np because the dns suffix are bn.local
but at homelocation when addressing the share via VPN f: on bnserver the dhcp at home adds its own dns suffix which could be teleadsl.dk
that means it cant resolve properly up against the server ...

so im told to make the shares as:
drive f: common_files @ bnserver.bn.local

and that should solve the dns lookup for the client ... because of the FQDN

this will be tested shortly and most likely Robbwill will get a partial solution .... the closest answer i think ...
and btw i can connect when using \\10.30.1.200\sharename ... also written in above text ...

thx guys...

DNS suffix were the solution.
thansk for a very fulsilling answer :)

Thanks cbcn,
--Rob