asked on

Routing and Remote Access denying VPN user access to domain controller

We have Routing and Remote Access running on Windows Server 2003. VPN users are able to successfully connect to this server and access MOST of the network drives and servers on network (same location and subnet). That is except for one, the domain controller and DNS server. VPN users, once connected, are not able to access the shared folders from explorer by either typing in the name or the ip address. Windows returns the error as if the server does not exist, although all other internal workstations and servers can get to this server just fine. The other thing that is strange is that a VPN users can successfully ping the domain/DNS server's IP address.
It seems like there may be an issue with RAS as though it won't let VPN users connect to that particular server. This happens for both XP and Vista users.

Also, the "hosts" file on each of the VPN user's systems is setup correctly.

Any ideas?

Amit Bhatnagar

I know it would be a li'l difficult but can you actually try and take a trace to see if the packets from the VPN Clients are even reaching the DC\DNS or not? A trace is very easy to read and if you want, I can help you reading it as well. You can install Netmon 3 or Wireshark on the DC\DNS to do the test. Both Softwares are free downloading and use.

Also, the DC\DNS...Is it in the same Network as other machines which you are able to access or not.

cciservices

ASKER

I found the solution. I ENABLED NetBios under the WINS tab for the network connection on the file server. Makes no sense to me (we do not use WINS), but it works perfectly now.

ASKER CERTIFIED SOLUTION

Amit Bhatnagar

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial