can't see computers over VPN

I have a Windows NT Server at location A. We use a workgroup, no domains.
No problem with computers at location A, seeing and accessing the server,
using TCP/IP and Windows Networking.

Have recently added location B. Two locations are connected by a VPN
through the internet. VPN is done with routers.

From location B, I can ping the server at location A, so I know the VPN is
working.

Problem is that I can't browse the files on the server, from location B. I
have verified the same workgroup, and subnet mask.

The two locations do not have the same IP address sequence. Would that be
the problem? If so, would I fix it by adding another NIC on the server,
addressing it in location B's range? I have heard that running two NICs on
NT Server did not work well. Is that true?

Browsing across WAN connections (including VPN) is frequently problematic.
The conventional solution is WINS. However, if you are only interested in
the shares on a server, why not simply use Start/Run \\NameorIPofServer
ENTER. If this works, you can create a shortcut on your desktop.

Doug Sherman
MCSE, MCSA, MCP+I, MVP

"CarSalesman" <(E-Mail Removed)> wrote in message
news:3521CBC8-FDD8-4584-980F-(E-Mail Removed)...
> I have a Windows NT Server at location A. We use a workgroup, no domains.
> No problem with computers at location A, seeing and accessing the server,
> using TCP/IP and Windows Networking.
>
> Have recently added location B. Two locations are connected by a VPN
> through the internet. VPN is done with routers.
>
> From location B, I can ping the server at location A, so I know the VPN is
> working.
>
> Problem is that I can't browse the files on the server, from location B.
I
> have verified the same workgroup, and subnet mask.
>
> The two locations do not have the same IP address sequence. Would that be
> the problem? If so, would I fix it by adding another NIC on the server,
> addressing it in location B's range? I have heard that running two NICs
on
> NT Server did not work well. Is that true?

Please tell me where I can learn how to set up WINS. I've seen WINS info in
the networking properties, but never understood what it is all about.

thank you,

don



"Doug Sherman [MVP]" wrote:

> Browsing across WAN connections (including VPN) is frequently problematic.
> The conventional solution is WINS. However, if you are only interested in
> the shares on a server, why not simply use Start/Run \\NameorIPofServer
> ENTER. If this works, you can create a shortcut on your desktop.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
> "CarSalesman" <(E-Mail Removed)> wrote in message
> news:3521CBC8-FDD8-4584-980F-(E-Mail Removed)...
> > I have a Windows NT Server at location A. We use a workgroup, no domains.
> > No problem with computers at location A, seeing and accessing the server,
> > using TCP/IP and Windows Networking.
> >
> > Have recently added location B. Two locations are connected by a VPN
> > through the internet. VPN is done with routers.
> >
> > From location B, I can ping the server at location A, so I know the VPN is
> > working.
> >
> > Problem is that I can't browse the files on the server, from location B.
> I
> > have verified the same workgroup, and subnet mask.
> >
> > The two locations do not have the same IP address sequence. Would that be
> > the problem? If so, would I fix it by adding another NIC on the server,
> > addressing it in location B's range? I have heard that running two NICs
> on
> > NT Server did not work well. Is that true?
>
>
>

Installation of the WINS server on your NT 4.0 machine is easy:

http://www.microsoft.com/resources/d...erver/proddocs
/en-us/rras40/rrasch04.mspx

This article will tell you more than you probably want to know about WINS:

http://www.microsoft.com/resources/d...erver/proddocs
/en-us/rras40/rrasch04.mspx

In your case all machines including the server should point to the server's
IP on the WINS tab in TCP/IP properties.

Doug Sherman
MCSE, MCSA, MCP+I, MVP


"CarSalesman" <(E-Mail Removed)> wrote in message
news:4F9DE443-5D89-4397-AEA2-(E-Mail Removed)...
> Please tell me where I can learn how to set up WINS. I've seen WINS info
in
> the networking properties, but never understood what it is all about.
>
> thank you,
>
> don
>
>
>
> "Doug Sherman [MVP]" wrote:
>
> > Browsing across WAN connections (including VPN) is frequently
problematic.
> > The conventional solution is WINS. However, if you are only interested
in
> > the shares on a server, why not simply use Start/Run \\NameorIPofServer
> > ENTER. If this works, you can create a shortcut on your desktop.
> >
> > Doug Sherman
> > MCSE, MCSA, MCP+I, MVP
> >
> > "CarSalesman" <(E-Mail Removed)> wrote in message
> > news:3521CBC8-FDD8-4584-980F-(E-Mail Removed)...
> > > I have a Windows NT Server at location A. We use a workgroup, no
domains.
> > > No problem with computers at location A, seeing and accessing the
server,
> > > using TCP/IP and Windows Networking.
> > >
> > > Have recently added location B. Two locations are connected by a VPN
> > > through the internet. VPN is done with routers.
> > >
> > > From location B, I can ping the server at location A, so I know the
VPN is
> > > working.
> > >
> > > Problem is that I can't browse the files on the server, from location
B.
> > I
> > > have verified the same workgroup, and subnet mask.
> > >
> > > The two locations do not have the same IP address sequence. Would
that be
> > > the problem? If so, would I fix it by adding another NIC on the
server,
> > > addressing it in location B's range? I have heard that running two
NICs
> > on
> > > NT Server did not work well. Is that true?
> >
> >
> >

I should add that installing WINS won't really solve all your browsing
problems in a workgroup situation. You will not be able to see a combined
browse list in Network Neighborhood or My network Places. Workgroups cannot
merge browse lists from different segments, whether they are linked by WAN
links or by routers. To merge browse lists you must have at least one domain
controller.

Doug Sherman [MVP] wrote:
> Installation of the WINS server on your NT 4.0 machine is easy:
>
> http://www.microsoft.com/resources/d...erver/proddocs
> /en-us/rras40/rrasch04.mspx
>
> This article will tell you more than you probably want to know about
> WINS:
>
> http://www.microsoft.com/resources/d...erver/proddocs
> /en-us/rras40/rrasch04.mspx
>
> In your case all machines including the server should point to the
> server's IP on the WINS tab in TCP/IP properties.
>
> Doug Sherman
> MCSE, MCSA, MCP+I, MVP
>
>
> "CarSalesman" <(E-Mail Removed)> wrote in message
> news:4F9DE443-5D89-4397-AEA2-(E-Mail Removed)...
>> Please tell me where I can learn how to set up WINS. I've seen WINS
>> info in the networking properties, but never understood what it is
>> all about.
>>
>> thank you,
>>
>> don
>>
>>
>>
>> "Doug Sherman [MVP]" wrote:
>>
>>> Browsing across WAN connections (including VPN) is frequently
>>> problematic. The conventional solution is WINS. However, if you
>>> are only interested in the shares on a server, why not simply use
>>> Start/Run \\NameorIPofServer ENTER. If this works, you can create
>>> a shortcut on your desktop.
>>>
>>> Doug Sherman
>>> MCSE, MCSA, MCP+I, MVP
>>>
>>> "CarSalesman" <(E-Mail Removed)> wrote in
>>> message news:3521CBC8-FDD8-4584-980F-(E-Mail Removed)...
>>>> I have a Windows NT Server at location A. We use a workgroup, no
>>>> domains. No problem with computers at location A, seeing and
>>>> accessing the server, using TCP/IP and Windows Networking.
>>>>
>>>> Have recently added location B. Two locations are connected by a
>>>> VPN through the internet. VPN is done with routers.
>>>>
>>>> From location B, I can ping the server at location A, so I know
>>>> the VPN is working.
>>>>
>>>> Problem is that I can't browse the files on the server, from
>>>> location B. I have verified the same workgroup, and subnet mask.
>>>>
>>>> The two locations do not have the same IP address sequence. Would
>>>> that be the problem? If so, would I fix it by adding another NIC
>>>> on the server, addressing it in location B's range? I have
>>>> heard that running two NICs on NT Server did not work well. Is
>>>> that true?