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.
