Can't remotely browse LAN 1

[anderoo]

Hello

I can connect to my W2K server using VPN, after setting up RRAS.
I used a differnet range of IP addresses for RRAS than my LAN.
Logging in from home to the server works like a dream and using terminal services is excellent, however this is as far as I can go.

I am unable to browse my work LAN or ping any of the IP addresses.

Any tips would be very useful.

Andrew

 

[ChicagoTechNet]

assuming the vpn server have two NICs, you may need to enable ip routing. quoted form

http://www.chicagotech.net/

How to Configure Windows server to Be a Router
To setup Windows 2000/2003 as a router for a LAN, you need to two network adapters. To enable LAN routing. go to Administrative Tools>Routing and Remote Access>Action>Configure and Enable Routing and Remote Access, and then complete the wizard. Right-click the server for which you want to enable routing, and then click Properties>General>Router, check Local area network (LAN) routing only, and then click OK.

Robert Lin, MS-MVP, MCSE & CNE
Windows, Network, Internet, VPN, Routing and How to at

http://www.ms-mvps.com

 

[anderoo]

Thanks Robert

I have only one NIC.

Is there any way around this without installing a second NIC

Andrew

 

[ChrisAC]

How are you doing name resolution when trying to browse the LAN over the VPN. Remember that netBIOS is based on broadcasts and so this won't over a routed connection. If your network has a WINS server then you could use this.

Chris.


**********************
Chris Andrew, CCNA, CCSA
chris@iproute.co.uk
**********************

 

[gacollier]

Andrew,

You're saying that your Win2K server has only one NIC or your machine at home? How is the VPN server seeing the LAN and WAN then if you server has only one NIC, port forwarding? Also, when you say that "I used a differnet range of IP addresses for RRAS than my LAN", that's probably the reason. Why didn't you use the same IP scheme as the LAN?
I'm guessing that this same server for VPN is also serving up the Terminal Server sessions as well, which would explain why it works, but you can't reach other LAN computers.

 

[anderoo]

ok
iproute
When I first established the VPN connection I configured my home PC (xp pro) to join my work domain. This worked as normal and my home computer then appeared in the AD (at work).
However on future VPN connections I am unable to join the domain.?
Network Neighbourhood on home PC now list work domain but won't let me browse the network.
I guess if I could rejoin the domain after the VPN connection, my problem could be solved.

Andrew

 

[anderoo]

gacollier,

My work PC has only one nic and my problem is that I can't see the LAN even though I have a VPN connection to the server.
I used a differnet range of IP addresses as my research before installing RRAS recommended this - perhaps this is incorrect.

Andrew

 

[gacollier]

Andrew,

I must admit, I'm still having some difficulty understanding the topology of your connection, but I'll press on. When you establish your VPN connection with the server, is the assigned IP address scheme (subnet) different from the LAN network scheme (subnet)? (i.e. LAN scheme = 10.1.X.X, VPN scheme = 10.2.X.X). If it is, then even if your VPN server was able to route between the two subnets, the hosts on the LAN won't route back to the VPN server. Have you tried changing the IP range on the VPN server to match the subnet on your LAN?

 

[ChrisAC]

The local network and the VPN network do not need to be on the same IP range. If the clients on the network have thier default gateway set correctly then they will be able to route the reply traffic back out of the network correctly via the VPN gateway. If the clients do not have a correctly set default gateway then you will not be able to ping them.

Chris.


**********************
Chris Andrew, CCNA, CCSA
chris@iproute.co.uk
**********************

 

[anderoo]

gacollier

I have changed the IP range on the VPN server to be within the IP range of my LAN and guess what?
I can access the rest of the network!

I can now from home access any PC.

I can also log into terminal servers on my w2k server and XP machines from home.

Would I be right in stating that I can't run a terminal server on a W2K professional client?

Other posts have suggested that I needed two nic on my server. I have avoided this by running my ADSL connection into my switch box, which seems to work very well. Is this okay to do this.

Many Thanks

Andrew

 

[gacollier]

Andrew,

Glad that worked.

There should be no problem running terminal server client on a Win2K pro machine. You'll just need to install the client, (should be located in "WINNT\system32\clients\tsclient" on the terminal server). If XP connects then you should be fine with your current config.

Post back if you need anything else.

 

[anderoo]

sorry gacollier

what I meant was that I presume I would need to set the w2k pro machines up as terminal servers so that I can access them, rather than these machines being the clients.

I don't think W2K clients clients can be set up as servers, in the way that winxp can

Many Thanks

Andrew

 

[gacollier]

Andrew,

Sorry but you kind of lost me again. Given that, let me take some pot shots...

If you're asking if you can run terminal services (or remote desktop) on a Win2K Pro machine, I think the answer is no. But, if you're looking to remotely control a Win2K machine you might want to look at something like PC Anywhere.

Are you looking to remote control these client computers or just access files or shared resources?