Discussion Locked

Cannot logon to domain over VPN tunnel

0 helpful
12 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I am at my wits end trying to get some Windows XP Pro users setup to work remotely through a VPN tunnel. They are able to connect, but not do anything domain-wise. I have read any and every article I can find with no resolution to this issue. Does anyone have an idea as to what may be causing the problem? Any help is appreciated. A Windows 2000 laptop that is a domain member, and a Windows XP Professional non-domain member are able to do more than the domain member laptops. Here is the setup:

Windows XP SP2 client (Laptops or workstation), Microsoft Windows 2000 AD domain members, IPSec VPN client (Netgear Safenet) or PPTP (Windows) client on laptops - same problem. Netgear FVS338 and Cisco PIX 501 firewall (PPTP) VPNs were tested. DNS & WINS in Mode Config, DNS & WINS in DHCP for desktop, SafeNet Virtual Adapter Interface on laptops, tunnel through hardware-to-hardware VPN for workstation, ZoneAlarm Security Suite Firewall on laptops, Symantec Anti-Virus on the workstation

On the LAN, domain authenticates, can connect to Exchange mailbox through Outlook 2003, can connect to mapped drives, can connect to terminal server

When over VPN, CAN PING ALL relevant addresses (so routing works), doesn't resolve names on corporate subnet, domain authentication doesn't work (actually takes 30 min. attempting), cannot connect to Exchange mailbox, mapped drives (neither by UNC nor by addressed UNC, e.g. \\192.168.xxx.xxx\sharename), nor to terminal server (event log says licensing problem), can connect to the workstations on LAN via VNC by address only

* disabling ZoneAlarm and/or Windows Firewall, nor adding exceptions in either software firewall doesn't fix it
* Plugging in static DNS and WINS addresses, nor LMHosts file entries make no difference
* Enabling Netbios on Netgear Firewall VPN makes no difference

Extensive tests with portqry.exe indicate that no ports are being filtered or blocked. WINS on server is working.

12 replies

by bfilmfan

These are the required AD ports:

Service Port/protocol
RPC endpoint mapper
135/tcp, 135/udp

NetBIOS name service
137/tcp, 137/udp

NetBIOS datagram service
138/udp

NetBIOS session service
139/tcp

RPC static port for AD replication
/tcp

SMB over IP (Microsoft-DS)
445/tcp, 445/udp

LDAP
389/tcp

LDAP over SSL
636/tcp

Global catalog LDAP
3268/tcp

Global catalog LDAP over SSL
3269/tcp

Kerberos
88/tcp, 88/udp

DNS
53/tcp, 53/udp

WINS resolution (if required)
1512/tcp, 1512/udp

WINS replication (if required)
42/tcp, 42/udp

The complete list of Microsoft Services and related ports can be found here:

http://support.microsoft.com/default.aspx?scid=kb;en-us;832017

One of your required ports is being blocked.

by bhalverson

Checked all the ports, all of them were available both on the local and through the VPN. Everything works fine with a Windows 2000 laptop, Windows XP Pro doesn't work, and I have tried literally everything. We are now planning to upgrade to Windows 2003, and go through ISA 2004 and a Terminal Server.

by blackcurrant

Hi

I had a similar problem when I setup a VPN to our (old) Win2k AD domain at work.

Users could connect to the network but no authentication took place. Users could not connect to any machine via machinename but could connect via local //ipaddress. So, typing //192.168.0.1 in I.E. would connect them to that machine, but, because no authentication had occurred, they could not access any shares.

I eventually resolved this by doing the following:

I added IP addresses and their corresponding computernames to the LMHOSTS file on the remote computers.

I asked each user for their login and password details on their remote machines (I asked them to create accounts specifically for the VPN). I then created identical account names and passwords on the router and also on the server. Then I configured each share with appropriate permissions.

What was happening was that the users were logging onto their machines using their home account/passwords, and then logging onto the router using their work accounts/passwords. The router (which I had configured with this information), then passed the details onto the Domain Controller. But, the Domain Controller was taking their *local* login details and not the information the router was passing through.

If each user had identical accounts/passwords for work and home, then I would not have had to create the extra accounts especially for the VPN.

Hope this helps

Good luck

by bhalverson

We cannot use the workgroup over domain option, because these laptops have to be domain members when in the office.

by billh

I would like to know that this indeed did solve your issue. My situation is much the same as described. I logged onto the system as local admin (NOT DOMAIN) and I was able to sync and map drives. When logged on to the domain remotely (cached credentials) I am unable to access/map drives - sync files. This would indicate the problem is NOT with firewall or blocked ports but with permissions.

by bhalverson

Answers did not help. We are going to upgrade to Windows SBS2003 because there is no other way to make this work correctly.

by parker

I hate to be the bearer of bad news, but upgrading to SBS 2003 will not resolve this.

I am currently facing a similar situation with two locations which are connected to a main office via router-router VPN tunnels:

Main office (SBS 2003 PDC, DNS1, WINS)
Remote office (Win 2003 BDC, DNS2, WINS)
Home office (workstation, Win 2003 server)

The home office workstation was originally a main office computer and is able to connect mapped drives on the PDC using cached credentials. The remote office was initially set up with a different WAN configuration but seems to be functioning fine since the cutover to VPN tunnels.

The home office server is not able to join the domain using "DOMAIN.LOCAL" but can join using the netbios name "DOMAIN".

However, when joined to the domain using only the netbios name, domain logon authentication fails each time (RPC error), and I can only logon with a local user account, making the domain membership essentially useless.

Ping and nslookup all return the correct results since both home office machines use the PDC as the primary DNS server and WINS server.

The only problem seems to be RPC, which is a pretty serious problem on an Active Directory based network.

Has anyone found a solution for RPC across a VPN connection?

by hornhonker

I had the same problem myself today, and after a lot of mucking around, I found out that disabled a Windows service that is normally not used for mundane domain browsing functions, but IS used to register with an AD domain, was the problem.

Check under Control Panel / Administrative Tools / Services

and see if the service "TCP/IP NetBIOS Helper" is enabled. If not, start it up and see if the WinXP workstation can register with the domain.

Once your PC has registered, you can safely disable it again - unless you plan on moving back and forwards between Workgroups and Domains on a regular basis.

Another top tip is to ensure that the MTU size of any LAN interfaces (including both wired and wireless ethernet ones) running over your VPN connection are reduced from 1500 bytes, to something a bit smaller - I use 1400 bytes myself.

Your VPN software probably has a utility to set this, but if you are using an external router or VPN hardware client, you will have to set this manually in the Windows registry.

Instructions on how to do this are found at:-

http://www.microsoft.com/technet/community/columns/cableguy/cg0704.mspx

Cheers,

Martin.

by ofori

Hi there i have the same problem at the moment using the a netgear DGFV338 firewall with its own vpn Client, did you manage solve the issue at all? thanks..

by bsui

I had the same problems, especially when loading outlook 2003 over the VPN. I finally put the server IP Address in the c:\windows\system32\drivers\etc\hosts file and when I pinged the name over the vpn it gave me the ip address back. I then loaded the outlook 2003 client and the mailbox connected and updated. Maybe that will help you.

This discussion is closed to new replies.