Can't see rest of network

[Mike Gray]

Hello,

I'm having problems seeing the rest of my network when I
am dialing up with RAS.

I can dial up and log into the server, but I cannot see
any other machines on the network.

I'm lost. Help.

GM

 

[Bill Grant]

The RAS link doesn't carry LAN broadcasts, so you won't see anything if
your LAN relies on broadcasts for name resolution. You will need to add an
LMHOSTS file to the remote client with entries for any machines on the LAN
it needs to contact by name.

If the LAN is using DNS or WINS, you should be able to use them. The
client should get the WINS and/or DNS addresses when it connects.

 

[Mike Gray]

That doesn't seem to help. Here is a little more info.

I have DNS and WINS running on the RAS server. I also
added entries in the LMHOST and HOST files(just in case).

My RAS server is also my Exchange2K server. I just
installed a new Exchange2K3 server and I am moving
mailboxes from the old server to the new server.

Everything internally works great.

I have some remote users on the old server, they use RAS
to dial up and sync their email using Outlook. If the
mailbox is on the old server it works fine, but if the
mailbox is on the new server, RAS cannot find the new
server.

I can access the Internet through RAS, but I cannot see
any workstations or servers in Network Neighborhood.

 

[Bill Grant]

There is no magic formula. You just need to know exactly what your
client is doing. W2k/XP clients will try both Netbios names and DNS names.
The only way to be certain what is happening is to monitor the traffic on
the VPN link (using Netmon or a third-party sniffer). This will tell you how
the remote is trying to access resources.

If the remote client gets the correct WINS address, it should be able to
get a browse list, because it can get the IP address of the DMB from WINS.
(If it can get a browse list, you should see the LAN machines in NN). If you
monitor the traffic, you should see a name server request to resolve the
special Netbios name <domainname 1b> , then a request for a browse list
to the received IP address.

Similarly wirh DNS. The client should get the DNS address at connection
time. If it is getting the correct DNS IP, it should be able to resolve DNS
names as long as it has the correct DNS suffix(es) configured in its TCP/IP
properties.

 

[Mike Gray]

thanks for your replys Bill,

But Sniffing is out of my league, I guess I will just
have to move my RAS server to my E2K3 server when all the
mailboxes are moved and hope it will work on the new
server like it did on the old server.

Thanks again.

MG

 

[Bill Grant]

W2k/W2k3 and E2k3 depend more heavily on DNS than NT and E2k did. So make
sure that your remote client gets the correct DNS address (ie the address of
your AD DNS server which has all the SRV records) and has the correct DNS
suffix(es) in its connection properties.