Can not access local resources over VPN

From: Dennis Grinberg (dgrin_bli_luef_at_bli_luef.bellatlantic.net)
Date: 11/17/04 

Date: Wed, 17 Nov 2004 16:33:13 -0500

I am connecting to my office via the VPN connection on a Windows XP SP2
machine. I installed the XP SP2 VPN patch. This is the setup:

- My home machine (laptop) has been registered on my office domain and I
login to the laptop with my domain credentials.

- My home network is on 10.0.0.X. The local network at work is using
192.168.X.X

- "Use default gateway on remote network" is checked on the VPN properties.
(I tried things without it as well.)

- I've tried my experiments choosing a Domain name when connecting as well
as leaving it blank

This is what I experience:

- When connected to VPN, I can access IP addresses on my home network
(10.0.0.X)

- When connected to the VPN, I can access external (public) IP addresses and
the routing goes from my office, not my home machine. Names resolve.

- I can access machines on my office domain via http

- I can not access network shares at my office. After a long timeout, I get
a message telling me to enter my credentials and that there was already an
attempt to authenticate based on the credentials I used to login with. I
enter credentials and it still fails.

- I can not ping any machines in my office network

- I can not perform name resolution for any machines at my office (the DNS
servers are set automatically by the VPN to local office IP addresses). [So
who is doing the resolution for the external sites?]

- I *can* RDP into machines on my office network.

I've read many similar posts but none of the suggestions seemed to be
applicable to my situation. Do you have any idea why I wouldn't be able to
access local shares and perform local name resolution? This is the main
reason I want access to the domain!

The one other quirky thing that could possibly be related is that the VPN
rejects my normal domain credentials and a new domain account needed to be
created so I could get into the VPN.

Thank you,

Dennis

Relevant Pages

  • Re: Vista, SBS 2003 and RAS not working
    ... We have a windows SBS 2003 server – straight out of the box, ... The VPN connection between your computer and the VPN server could not ... You mention that the clients are Vista machines, which means that their built-in firewall works on outgoing messages as well as incoming ones, and the firewall needs to be told that outgoing PPTP VPN connections should be allowed. ... Computers don't need to be joined to the domain to connect by VPN, by the way, so you can use other remote computers for testing, it's just that only domain machines get access to all network resources easily. ...
    (microsoft.public.windows.server.sbs)
  • RE: SBS 2003 and shared folders through VPN
    ... SBS 2003 Shares over VPN ... Corporate information is shared on folder "Main" there is also the network ... Firewall is providing the VPN over a T1 circuit. ... | has no problems connecting to the internet nor is the share drives not ...
    (microsoft.public.windows.server.sbs)
  • Re: VPN and XP SP2 woes
    ... Stock MS VPN, ... Employer's network is NT. ... >> Is your VPN connection using only Microsoft software or is it third ... >>> with both machines and the results were identical. ...
    (microsoft.public.windowsxp.help_and_support)
  • VPN and XP SP2 woes
    ... I installed SP2 a week ago from stand-alone offline install file. ... All has been working fine with both machines and I am quite happy with the ... Today I needed to access my employer's private network via VPN connection. ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: VPN users are unable to access the private network =/
    ... I can ping BOTH interfaces on the VPN server ... I can reach machines on the network if I forward specific ports to the ...
    (microsoft.public.win2000.networking)