Questions

VPN will Connect but can not map drive

+
1 Votes
Locked

VPN will Connect but can not map drive

bigos2
I set up a VPN on a windows XP at home and set up Server 2003 to except VPN. At home I can log on to server, but I can't map drives, read data, etc. Can anybody help me. What am i forgetting?
+
0 Votes
vlape
Collapse -

can you see the shares by \\<server name>, if not how bout \\<ip address>?
post output from ipconfig /all of the VPN connection.

+
0 Votes
luc_andre
Collapse -

If you have a software firewall, like Norton Security, it could be blocking the allowance of network connections like File Sharing and NetBios (in Norton, found under Advanced Settings > Networking)

+
0 Votes
Kjell_Andorsen
Collapse -

I have seen the same issue, it appears to be a shortcoming of XP home. It has issues connecting to certain network reosurces on a Domain. Only way I found around it was to upgrade the end-user to XP pro, which instantly resolved the issue.

I believe it's an issue with XP home not authenticating properly to an AD Domain.

+
0 Votes
vlape
Collapse -

I have never had an issue with XP Home or Media edition authenticating against a domain via VPN. The operating system has no relevance. if DHCP is not passing thru the proper information such as domain suffix, dns, gateway because the firewall is not configured to do as such you will have a problem accessing network resources by name.

Installing another operating system is NOT the answer to this problem. Proper configuration of your firewall is the solution.

+
0 Votes
Kjell_Andorsen
Collapse -

I've had the Win XP Home users AUTHENTICATE and be able to log on to VPN, that was not the problem, but the problem is that because XP home doesn't support Group policy and File level access control, they were not able to access network drives and folders on the network once they had logged on to the domain. This appears to be the problem the poster is having, and I don't really see it as being a firewall issue. The test is of course to simply disable the firewall on the VPN client and see if it works.

+
0 Votes
vlape
Collapse -

i am not going to get into a flame match with you about this however you are WAY off the mark here. A NON DOMAIN computer making a VPN connection to a domain will NEVER process a gp. the workstation does not even know the domain controller exists. File access control had nothing to do with the clent computer being part of the domain, this is why users have the ability to auth with user@domain or domain\user. This authentication is done when the VPN connection is established. (remember the user is authenticating NOT the machine)

This is nothing more than a firewall configuration issue. The firewall is not handling dns from vpn side to internal and most likeley the user did not properly setup dhcp relay agent or configure dhcp properly therefore the client pc is not getting enough information to use netbios names over the netowrk. I would bet anything he can connect using IP addresses to everything on his netowrk wothout any problems.

I am sure the poster appriciates your help / information however if you do not completely know that you are talking about and provide incorrect informaiton it will only add confusion to the situation. Anyhow just my two cents.

+
0 Votes
scottmelcher
Collapse -

I have set up my XP home to accept incoming connections via a VPN. I am able to connect to this VPN fine from outside my network. However, I cannot then map a drive. I have tried disabling the firewall to no avail.

+
0 Votes
scottmelcher
Collapse -

I am also trying to map the drives via IP address and not name.

+
0 Votes
ameza
Collapse -

how many network adapters do you have on the server? for full VPN functionality you need two.
see: http://support.microsoft.com/kb/217766/en-us