NickRamsey
asked on
VPN from Workgroup computer to Domain server - no domain resources visible
I have a Windows 2003 server running on the internet and accepting a RAS connection via VPN.
However I can see none of the shared resources on the domain/server from the VPN client.
My laptop machine runs XP Pro and I have set up a VPN connection on it.
However, the client is not a member of the Domain the server is in. It is a member of a workgroup (which I have given the same name as the domain).
The client can connect to the server over the internet quite happily.
I am challenged for Username, password and Domain and these are accepted.
The username/password on the workgroup laptop matches my account on the domain.
The internal IP range on the domain LAN is 192.168.16.x
The VPN gets issued a dynamic address in the domain's subnet and also is issued the same address (i.e. the client's address) as the gateway.
Browsing on the XP Pro workgroup client does not show any of the machines or shares on the Domain. Trying to open (via Start->Run) the server IP address fails. Trying to open the server share by name in Explorer fails.
I can ping the internal (domain) IP address of the server and of a wirelss access point that is sitting on the domain LAN. So IP is getting routed properly by the looks of it.
Can anybody suggest why I can do all this, but not see the server, nor connect to it by IP address or name?
Thanks for any help!
However I can see none of the shared resources on the domain/server from the VPN client.
My laptop machine runs XP Pro and I have set up a VPN connection on it.
However, the client is not a member of the Domain the server is in. It is a member of a workgroup (which I have given the same name as the domain).
The client can connect to the server over the internet quite happily.
I am challenged for Username, password and Domain and these are accepted.
The username/password on the workgroup laptop matches my account on the domain.
The internal IP range on the domain LAN is 192.168.16.x
The VPN gets issued a dynamic address in the domain's subnet and also is issued the same address (i.e. the client's address) as the gateway.
Browsing on the XP Pro workgroup client does not show any of the machines or shares on the Domain. Trying to open (via Start->Run) the server IP address fails. Trying to open the server share by name in Explorer fails.
I can ping the internal (domain) IP address of the server and of a wirelss access point that is sitting on the domain LAN. So IP is getting routed properly by the looks of it.
Can anybody suggest why I can do all this, but not see the server, nor connect to it by IP address or name?
Thanks for any help!
Good to know...I've been curious on this one. Congrats.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Bizarre default rule to have, but changing it allowed me to see resources.
Nick