Can not access local resources over VPN

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

too many issues on this post. let me ask a simple question. Can you ping the
office server by ip? if yes, can you ping it by name? if you can't ping ip,
post the results of vpn client ipconfig /all here.

--
For more and other information, go to http://www.ChicagoTech.net

Don't send e-mail or reply to me except you need consulting services.
Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
http://www.ChicagoTech.net
Networking Solutions, http://www.chicagotech.net/networksolutions.htm
VPN Solutions, http://www.chicagotech.net/vpnsolutions.htm
VPN Process and Error Analysis, http://www.chicagotech.net/VPN%20process.htm
VPN Troubleshooting, http://www.chicagotech.net/vpn.htm
This posting is provided "AS IS" with no warranties.
"Dennis Grinberg" <dgrin_bli_luef@bli_luef.bellatlantic.net> wrote in
message news:(E-Mail Removed)...
>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
>
>
>
>

One thing to bear in mind is that the usename you use to create the VPN
connection is not necessarily what the client will use to access resources.
It may be using the credentials of your original local login. Would that be
valid on your office domain?

"Dennis Grinberg" <dgrin_bli_luef@bli_luef.bellatlantic.net> wrote in
message news:(E-Mail Removed)...
>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
>
>
>
>

I can not ping any office server. The ipconfig results for the VPN client
(with sanitized addresses)

Windows IP Configuration

Host Name . . . . . . . . . . . . : laptop09
Primary Dns Suffix . . . . . . . : local.foo.com
Node Type . . . . . . . . . . . . : Hybrid
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : local.foo.com
foo.com

Ethernet adapter Wireless Network Connection:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : NETGEAR 108 Mbps Wireless PC
Card WG511T
Physical Address. . . . . . . . . : 00-09-5C-C4-0C-E8
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.0.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.0.1
DHCP Server . . . . . . . . . . . : 10.0.0.1
DNS Servers . . . . . . . . . . . : 10.0.0.1
Lease Obtained. . . . . . . . . . : Wednesday, November 17, 2004
7:49:29 PM
Lease Expires . . . . . . . . . . : Thursday, November 18, 2004
7:49:29 PM

PPP adapter Matrix Solutions:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.190.70
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . : 192.168.190.70
DNS Servers . . . . . . . . . . . : 192.168.190.100
192.168.190.200
Primary WINS Server . . . . . . . : 192.168.190.100


"Robert L [MS-MVP]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> too many issues on this post. let me ask a simple question. Can you ping
> the office server by ip? if yes, can you ping it by name? if you can't
> ping ip, post the results of vpn client ipconfig /all here.
>
> --
> For more and other information, go to http://www.ChicagoTech.net
>
> Don't send e-mail or reply to me except you need consulting services.
> Posting on MS newsgroup will benefit all readers and you may get more
> help.
>
> Bob Lin, MS-MVP, MCSE & CNE
> Networking, Internet, Routing, VPN, Anti-Virus, Tips & Troubleshooting on
> http://www.ChicagoTech.net
> Networking Solutions, http://www.chicagotech.net/networksolutions.htm
> VPN Solutions, http://www.chicagotech.net/vpnsolutions.htm
> VPN Process and Error Analysis,
> http://www.chicagotech.net/VPN%20process.htm
> VPN Troubleshooting, http://www.chicagotech.net/vpn.htm
> This posting is provided "AS IS" with no warranties.
> "Dennis Grinberg" <dgrin_bli_luef@bli_luef.bellatlantic.net> wrote in
> message news:(E-Mail Removed)...
>>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
>>
>>
>>
>>
>
>

Yes, they are valid.


"Bill Grant" <not.available@online> wrote in message
news:%(E-Mail Removed)...
> One thing to bear in mind is that the usename you use to create the VPN
> connection is not necessarily what the client will use to access
> resources. It may be using the credentials of your original local login.
> Would that be valid on your office domain?
>
> "Dennis Grinberg" <dgrin_bli_luef@bli_luef.bellatlantic.net> wrote in
> message news:(E-Mail Removed)...
>>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
>>
>>
>>
>>
>
>

A bit more information: If I try to browse to a machine via IP address, I
get a dialog box asking for my credentials. When I enter my laptop
credentals (which are valid) and I get tooltip which reads:

The user name you typed is the same as the user name you logged in with.
That user name has already been tried. A domain controller can not be found
to verify that user name.



I tried entering other valid domain credentials which also did not work
(although I didn't get the tip). I then entered some local credentials for
the machine at the IP address in question and I was able to access the
machine (locally).



Dennis



"Dennis Grinberg" <dgrin_bli_luef@bli_luef.bellatlantic.net> wrote in
message news:uVP%(E-Mail Removed)...
> Yes, they are valid.
>
>
> "Bill Grant" <not.available@online> wrote in message
> news:%(E-Mail Removed)...
>> One thing to bear in mind is that the usename you use to create the
>> VPN connection is not necessarily what the client will use to access
>> resources. It may be using the credentials of your original local login.
>> Would that be valid on your office domain?
>>
>> "Dennis Grinberg" <dgrin_bli_luef@bli_luef.bellatlantic.net> wrote in
>> message news:(E-Mail Removed)...
>>>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
>>>
>>>
>>>
>>>
>>
>>
>
>