Unable to see subnets

  • Thread starter Thread starter Grant
  • Start date Start date
G

Grant

Ive setup a standard VPN server on the Windows 2003 server. The problem is
users can connect and browse the local subnet (192.168.200.1/254) but cannot
get to any of our other subnets (192.168.1.1/254 or 192.168.1.10/254)

I have to get them to enter the hostname and IP address into the hosts file
for them to be able to connect to a machine on another subnet.

I tried using the following command:
route add 192.168.1.0 mask 255.255.255.0 192.168.200.1

but that failed to work. There must be a setting somewhere on the server
that Ive missed when I was setting it up - I used mostly default settings.
Can anyone give me any advice on this please? The server has 2 network
cards, and if you ned any configuration or settings Ill be happy to post.

Thanks,
Grant
 
we need more information to help. how do you connect to the 192.168.1.o network? posting the routing table may help.
For more and other information, go to http://howtonetworking.com.

Don't send e-mail or reply to me except you need consulting services. Posting on MS newsgroup will benefit all readers and you may get more help.

Bob Lin, MS-MVP, MCSE & CNE
How to Setup Windows, Network, Remote Access on http://www.HowToNetworking.com
Networking, Internet, Routing, VPN Troubleshooting on http://www.ChicagoTech.net
This posting is provided "AS IS" with no warranties.

Ive setup a standard VPN server on the Windows 2003 server. The problem is
users can connect and browse the local subnet (192.168.200.1/254) but cannot
get to any of our other subnets (192.168.1.1/254 or 192.168.1.10/254)

I have to get them to enter the hostname and IP address into the hosts file
for them to be able to connect to a machine on another subnet.

I tried using the following command:
route add 192.168.1.0 mask 255.255.255.0 192.168.200.1

but that failed to work. There must be a setting somewhere on the server
that Ive missed when I was setting it up - I used mostly default settings.
Can anyone give me any advice on this please? The server has 2 network
cards, and if you ned any configuration or settings Ill be happy to post.

Thanks,
Grant
 
You seem a bit confused about what is happening. If it works when you
put an entry in the hosts file, routing is working. What is not working is
name resolution. This is quite common over VPN.

Browsing across a WAN is pretty complicated. Are you running WINS and a
domain on the LAN? Can the clients in 192.168.1 browse the whole network?
 
Yes we have Wins and DNS running on the LAN/WAN. Internally, clients can
browse across subnets fine ie '192.168.1' clients can see '192.168.200'
subnet and vice versa. Its just when clients connect to the VPN server on
the '192.168.200' subnet that they are unable to see the '192.168.1' subnet.
Do you think it could be a WINS issue?
 
It is a computer browser problem. But browsing across routers/WAN links
requires WINS.

Are the remote clients domain members? To get a browse list, they need
to be able to find the domain master browser. This will fail if they don't
know the domain's Netbios name. They find the browse master by sending a
name request for <domainname 1B> to WINS. (You can check what they actually
send by monitoring the traffic coming over the VPN link).
 
The VPN server has 2 NIC's and only one of them was registered with the Wins
server on the other subnet. I kept getting event 4102:

---------------
The connection was aborted by the remote WINS. Remote WINS may not be
configured to replicate with the server.
---------------

So Ive added the 2nd NIC address to WINS replication and I'll see if that
sorts out the VPN browser problem.

Thanks for your help with this.

Cheers,
Grant
 
That could cause you more problems than it solves. Having Netbios active
on more than one interface can cause all sorts of problems (especially if it
is a DC or a browse master). That includes the "internal" interface of the
VPN server. See KB 292822 and 830063 .
 
Back
Top