Browser failure for the remote subnet.

We have a single Windows 2000 server in a workgroup configuration, not an
active directory. We have 2 VPN routers, locations 1 & 2 and are able to ping
the internal IP addresses from (within) router to router. After rebooting
the server, remote location(XPpro) is able to see mapped network drive.
Remote location uses terminal services as well as PC Anywhere during the day.
Server address is 192.168.0.3 and the internal address for remote worksation
is 192.168.1.5. Both routers have static IPs.(Also after a period of time
the VPN will sometimes will go down, and I have to re-activate the VPN by an
internal ping to the remote from within the router and the VPN will activate)
Sometime during the course of the day, for some unknown reason, the mappped
drives drop. Now here's what's strange. I have VNC on the server running, and
when you put the pointer over it, it normally gives you the IP address of the
network adapter. However, what is strange is that sometime later during the
day, when you put the pointer over it, it not only has the 192.168.0.3, the
192.168.1.5 seems to attach to this network card also. If I reboot the
remote workstation, the problem remains the same. I have to reboot the
server in order for it to show only the 192.168.0.3 when I put the pointer
over the VNC tray icon, and the mapped drives become accessible. Again,
sometime during the day, whether they logoff and log back on again, or not,
the mapped drives become inaccessible again. I have the server IP address and
name in the host file on the remote as well as on the server, as well as the
LMhost file on both. WINS is running. as well as DNS (although we have a
workgroup enviorment and I'm not sure it is set up correctly) , the latter I
set up this morning.

Any and all suggestions will be greatly appreciated, even things that I may
have overlooked concerning what I've already mentioned.

Thanks,
AMD

A workgroup setup for a WAN and both PC Anywhere and VNC sounds like a
nightmare to me!

The basic problem is probably the fact that, once a server accepts a VPN
connection it becomes multihomed. Have a look at the KB articles 289735 and
292822. They assume a domain setup, so they will not be directly applicable
but they outline the problem of multihomed servers due to remote access. You
probably have multiple entries in WINS for the servers.

"AMD" <(E-Mail Removed)> wrote in message
news:42E91C1F-E866-4EE5-B5F5-(E-Mail Removed)...
> We have a single Windows 2000 server in a workgroup configuration, not an
> active directory. We have 2 VPN routers, locations 1 & 2 and are able to
> ping
> the internal IP addresses from (within) router to router. After rebooting
> the server, remote location(XPpro) is able to see mapped network drive.
> Remote location uses terminal services as well as PC Anywhere during the
> day.
> Server address is 192.168.0.3 and the internal address for remote
> worksation
> is 192.168.1.5. Both routers have static IPs.(Also after a period of time
> the VPN will sometimes will go down, and I have to re-activate the VPN by
> an
> internal ping to the remote from within the router and the VPN will
> activate)
> Sometime during the course of the day, for some unknown reason, the
> mappped
> drives drop. Now here's what's strange. I have VNC on the server running,
> and
> when you put the pointer over it, it normally gives you the IP address of
> the
> network adapter. However, what is strange is that sometime later during
> the
> day, when you put the pointer over it, it not only has the 192.168.0.3,
> the
> 192.168.1.5 seems to attach to this network card also. If I reboot the
> remote workstation, the problem remains the same. I have to reboot the
> server in order for it to show only the 192.168.0.3 when I put the pointer
> over the VNC tray icon, and the mapped drives become accessible. Again,
> sometime during the day, whether they logoff and log back on again, or
> not,
> the mapped drives become inaccessible again. I have the server IP address
> and
> name in the host file on the remote as well as on the server, as well as
> the
> LMhost file on both. WINS is running. as well as DNS (although we have a
> workgroup enviorment and I'm not sure it is set up correctly) , the latter
> I
> set up this morning.
>
> Any and all suggestions will be greatly appreciated, even things that I
> may
> have overlooked concerning what I've already mentioned.
>
> Thanks,
> AMD

Without the presence of at least 1 domain to merge the browse
list across the WAN browsing will not occur. Browsing across
remote workgroups is not possible.

"AMD" <(E-Mail Removed)> wrote in message news:
> We have a single Windows 2000 server in a workgroup configuration, not
an
> active directory. We have 2 VPN routers, locations 1 & 2 and are able
to ping
> the internal IP addresses from (within) router to router. After
rebooting
> the server, remote location(XPpro) is able to see mapped network
drive.
> Remote location uses terminal services as well as PC Anywhere during
the day.
> Server address is 192.168.0.3 and the internal address for remote
worksation
> is 192.168.1.5. Both routers have static IPs.(Also after a period of
time
> the VPN will sometimes will go down, and I have to re-activate the VPN
by an
> internal ping to the remote from within the router and the VPN will
activate)
> Sometime during the course of the day, for some unknown reason, the
mappped
> drives drop. Now here's what's strange. I have VNC on the server
running, and
> when you put the pointer over it, it normally gives you the IP address
of the
> network adapter. However, what is strange is that sometime later
during the
> day, when you put the pointer over it, it not only has the
192.168.0.3, the
> 192.168.1.5 seems to attach to this network card also. If I reboot
the
> remote workstation, the problem remains the same. I have to reboot
the
> server in order for it to show only the 192.168.0.3 when I put the
pointer
> over the VNC tray icon, and the mapped drives become accessible.
Again,
> sometime during the day, whether they logoff and log back on again, or
not,
> the mapped drives become inaccessible again. I have the server IP
address and
> name in the host file on the remote as well as on the server, as well
as the
> LMhost file on both. WINS is running. as well as DNS (although we have
a
> workgroup enviorment and I'm not sure it is set up correctly) , the
latter I
> set up this morning.
>
> Any and all suggestions will be greatly appreciated, even things that
I may
> have overlooked concerning what I've already mentioned.
>
> Thanks,
> AMD