Need to see Network Places over VPN, NETGEAR, Windows XP, DNS, WAN

I need exact instructions for getting the DNS functionality working
and showing the Network Places/Network Neighborhood. I can obviously
see the computer on the local network (HOME) but cannot see the
computer on the remote network (WORK). And from WORK vise versa.

How they are set up:

They are connected by VPN. HOME is a NETGEAR FVS318. WORK is a NETGEAR
FVS328. The connections have been established and are set up exactly
like Appendix G of the NETGEAR FVS328 case study on how to configure a
VPN tunnel between a FVS318 and FVS328. Here is a link:

ftp://downloads.netgear.com/files/fvs328_ref_man.pdf

I can ping any computer on either networks LAN IP address with no
problem. I can browse any computer via its LAN IP address. i.e. From
HOME which is 10.5.6.1 IP range I can ping and browse WORKs
192.168.0.1 or any other IP in the range 192.168.0.3 for instance.
Both routers have the 1st address in there respective range in their
networks.

I just can?t see the computer names in Network Places. 

There are only XP Pro computers in the network. 

I would prefer not to us a LMHOST solution. 

My understanding is that XP should handle this through DNS out of the
box and doesn?t rely on NETBIOS.

It'll only handle via DNS if you have a DNS server. XP Pro does not
(IIRC) include a DNS server.

It is important that your home computer have the same workgroup/domain
name as the LAN. When you connect via VPN, your XP Pro (HOME) must
find a way to register itself on the VPN DNS. (That is, one of the DNS
IPs must be the DNS server of your Office LAN.)

Also, it's important to make sure that your standard RPC and SMB ports
aren't blocked on either side. They might be blocked normally by
firewall software as safe practice.

I need exact directions to get from where I am (described above) to
where I want to go (described above)

Thanks for the help but I need better directions.

1) Get a Windows server that handles DNS at WORK. If you don't know
what I'm talking about at this point, the rest of the answer is
immaterial.
2) Change the DNS of the home PC to the IP of the server that handles DNS
3) Change your workgroup of your home PC to the workgroup/domain name of your LAN

If you need specific instructions on any of these steps, please
indicate. Since I'm just repeating what I said above, this is probably
not helping you much.

You said "There are only XP Pro computers in the network." Which
indicates to me that you don't have a server. So part of the issue is
that you don't have a Windows 2000/2003 server that handles DNS.

You will need to make sure ALL ports (especially 135) are being passed
through your VPN.

You have really two issues. DNS won't work out of the box without a
DNS server to handle the connections. RPC location and filesharing
won't work if a firewall is blocking ports 135-139 TCP and UDP. Your
best bet is to make sure your VPN sees your home computer unencumbered
by any firewall on the IP set that you're using. So, what kind of
firewall could you have on your home PC? Whatever it is, you might
turn it off or "Trust" the VPN connection. It's likely that the VPN
hardware may be blocking certain points as well.

Regardless, unless your home computer has a place to announce that it
is on your work network, it cannot do it. Especially if you don't use
netbios. If your home computer is not on the same domain/workgroup as
your office, you won't see any computers listed. And they won't
announce to you.

You are correct I don't have a Windows 2000/2003 server anywhere in
the network. I will need to solve the problem another way. If what you
are saying is correct it sounds like I may have to consider a LMHOST
solution. I was think that the routers might be able to pass the
information so that the networks looks local.

I read over appendix G as well as other relevant pieces of the manual.
If you have checked the enable netbios setting on both routers(Refer
to Fig. G-5 and Fig G-10 in Appendix G), you should, in theory be able
to browse your network neighborhood.

As it sounds as if this is not the case I would recommend checking
your HOME computer for a firewall of some sort, i.e. Sygate, Norton,
McAfee etc. If you are running a firewall look for settings related to
file and print sharing.

Also under your network connection properties make sure File and Print
Sharing for Microsoft Networks is listed. If not it can be installed
by clicking the install button in your network connection properties
and then selecting Service. Note: this should be installed by default.

Also under the network connection properties you should look under
under the properties for Internet Protocol(TCP/IP) and click on the
advanced button. Go to the WINS tab and make sure that Enable NetBios
over TCP/IP is selected.

To eliminate confusion your workgroup name should match the workgroup
name of your WORK network. This can be set under the properties for My
Compute, Specifically the Computer Name Tab. Since it sounds as if you
are not running a windows Domain this is NOT necessary will make it
easier to navigate your WORK network once things are working properly.

Hope this helps a bit,

alby