VPN - Viewing external LAN

Soldato
Joined
31 May 2005
Posts
15,640
Location
Nottingham
OK.

I have successfully created a VPN connection with a remote PC in XP and am shown as connected.

When trying to view Workgroup computers, all I see is my own.

Both computers are on the same Workgroup, is there anything else which needs to be enabled to allow me to access the remote LAN?

There are no firewalls installed for diagnostic purposes and no routers are involved.
 
i believe you have to put your remote domain's name in the domain box when you connect via the connection? this is a guess as i wanted to connect to the local college network and mucked about and i think that did it :confused:
 
You've created a VPN connection with a single machine - not to a subnet of machines. I think that you do what you want you'd need a VPN connection to each machine that you'd want to see.
 
sja360 said:
i believe you have to put your remote domain's name in the domain box when you connect via the connection? this is a guess as i wanted to connect to the local college network and mucked about and i think that did it :confused:

SO it needs to be a member of a Domain, NOT a workgroup?

burbleflop said:
You've created a VPN connection with a single machine - not to a subnet of machines. I think that you do what you want you'd need a VPN connection to each machine that you'd want to see.

Please could you elaborate, I dont quiet follow, sorry.

I have created a VPN host on my PC which is running and other computers can connect to and same on the remote PC... but when either connect to the other VPN, the Local network cannot be seen.
 
AFAIK the "VPN Server" functionality in windows xp is very limited. There won't be any routing available, so all you can do is connect to the remote PC with a VPN connection, you can go no further.

If you want to do any more you will need to get windows server edition.

Or your remote router/firewall might support vpn endpoints.
 
oddjob62 said:
AFAIK the "VPN Server" functionality in windows xp is very limited. There won't be any routing available, so all you can do is connect to the remote PC with a VPN connection, you can go no further.

If you want to do any more you will need to get windows server edition.

Or your remote router/firewall might support vpn endpoints.

That's what I was trying to say, but I worded it pretty badly.
 
how's it setup at the minute? i mean i guess there isnt a lot on that lan network atm apart from a few workstations?
 
sja360 said:
how's it setup at the minute? i mean i guess there isnt a lot on that lan network atm apart from a few workstations?

Correct, 2 Workstations.

Im almost positive this can be done with XP PRO.. Maybe wrong though
 
in that case i think these guys are right you need to have a server edition of the os to get access to network resources.
 
As in Server 2003?

Can this be used a replacement for XP in standalone use.. Ie playing games etc.. does it support XP drivers?
 
play games and stuff no, the server edition is for the lan side to which your connecting not at your end (client), you'd have server 2003 providing a vpn service i believe.
 
thing is xp is only a workstation os really, it didnt require the vpn/domains etc features like the server editions did, if it did have those abilities there'd be no point to the server 2000/2003 etc.
 
Gimpymoo said:
I dont understand MS logic in not allowing this in XP as surely this has more benefits over Remote Remote desktop?

Quite simply the XP OS is designed as a client OS. If you could VPN to it an access the rest of the LAN then some people would not purchase Win2k3 Server.

In the same way that XP Pro will only allow 10 concurrent incoming network connections, etc.

Basically it's their way of saying "if you need more functions, upgrade"
 
Back
Top Bottom