VPN connection ok, but no shares

Archived from groups: comp.dcom.vpn (More info?)

try to map using ip addresses vs names ie \\192.168.0.x\sharename
look at host file
lmhost file # preload your windows domain servers
you may need to put your addresses & server addresses in there
may also try pointing a dns entry on the remote to your internal dns


"Peter Brühlmann" <lonerider@seznam.cz> wrote in message
news:1103456173.043870.138640@f14g2000cwb.googlegroups.com...
> I have a VPN connection (the Windows XP "System" ) from my home notebook
> to the office. It worked fine for weeks but now no longer. VPN is still
> loging in without problems. Ipconfig /all shows my notebook as
> 192.168.2.100 in the lan at home and 192.168.0.208 connected with PPP
> Adapter (this is within the address range my office PC gives to the
> incoming VPN connection). In the office the VPN connection at my PC is
> to be seen as ok and connected. But I cannot connect to any of the
> shared drives (I don't even see a root directory) and the remote
> desktop doesn't work. I use classical file sharing with a test
> directory open for everyone and the windows remote desktop (VNC doesn't
> work either). The usernames and passwords on all machines are the same.
> If I connect to the Office LAN locally everything is fine! Certainly I
> (?) have changed something, but what, I am completly irritated?
>
> My OS Win XP Pro SP-2 with teh XP Firewall (VPN Ports/Remote Desktop
> are open)
>

Archived from groups: comp.dcom.vpn (More info?)

On Mon, 20 Dec 2004 14:55:53 GMT, "Looker" <Xlookd@Xdhsinc.com> wrote:

>try to map using ip addresses vs names ie \\192.168.0.x\sharename
>look at host file
>lmhost file # preload your windows domain servers
>you may need to put your addresses & server addresses in there
>may also try pointing a dns entry on the remote to your internal dns
>
>
You wont see netbios names -- must use IP addreses instead. It can be
a problem when all stuff is DHCP-ed. That's why there is better to
assign static IP to the computer with shares and put the appropriate
association into "hosts" file. In fact it has a very little sense to
DHCP a comp with permanently used shares. DHCP is for dynamic
connection. In a small LAN all should be set static!!!! Leave a small
range for guests only!

Or use remote access server inside LAN (you must allow IPsec to go
through 47 and 1723 ports) for DHCPing the remote computer and
NetBios' names redirection (does someone remember a dial-up server in
Windows 95? -- it worked this way).

Tomek