VPN problems

I am having a problem with a VPN user=2E I have tested the co0nnection from a seperate computer and can get in with out a problem=2E

Ok this is the problem I am getting with one specific user and her machine=2E She can log into the VPN=2E=2E she cannot browse the network but she can ping by name both netbios and DNS=2E When i view network neigborhood I only see one machine and that is a mapped drive=2E If I try to connect via UNC I get the network path not found\\10=2E44=2E12=2E99 or use the IP address=2E I am stuck at this point so any advice gratefully recieved=2E=2E=2E

In case someone else has not asked, is the account that the VPN'd
user is logging in with the Network/Domain login or their local machine
account? If it is the local account, it might explain why the resources
are not available.

Other machines are working but this one isn't, I see what your saying but I
have checked other machines other accounts.

This is the scenario..

From the machine I want to VPN in with..
Log on with a domain account
Connect to the VPN with a domain account and authenticate OK
Can ping by name i.e PING machine ok
Can ping by FQDN i.e PING machine.abc.com ok
Can connect to mail server and send receive mail OK

have u tried logging in with another user on that specific machine?
and try the user to logon from another machine and see what happens. that way you can isolate the problem and see if its user or system related problem.

Did your VPN user login to the domain? I remember their being a scroll down arrow in the VPN window my company used and the first time I logged in from home and went back to the office with my laptop I forgot to change it back and got what you described below.

Dino
"Some people spend an entire lifetime wondering if they made a difference.
The Marines don't have that problem."

SYMPTOMS
After you establish a virtual private network (VPN) connection with a server, you cannot connect to any shares on the server. You can ping the server by name and Internet Protocol (IP) address, but cannot connect to shares on the server. Net View and Net Use commands fail with one of the following error messages:
System error 121. The semaphore timeout period has expired
System error 53. The network path was not found.
System error 64. The specified network name is no longer available.

CAUSE
This problem occurs because the TCP window size for the TCP connection for the VPN client is 0 (zero).

RESOLUTION
Service Pack Information
To resolve this problem, obtain the latest service pack for Microsoft Windows 2000. For additional information, click the following article number to view the article in the Microsoft Knowledge Base:

Copyright 1998-2015 Ziff Davis, LLC (Toolbox.com). All rights reserved. All product names are trademarks of their respective companies. Toolbox.com is not
affiliated with or endorsed by any company listed at this site.