Two networks connected by VPN

[DJPogoff]

I have two small WORKGROUP networks, about 6 machines in each: network
10.0.0.0/24 and 10.0.1.0/24 at different sites connected by a VPN. Hosts on
each network can see hosts on the other network _only_ in terms of IP
address. How can I allow the two networks to see each other by host name?
(Am I talking about "NetBIOS name"?)

I suppose that the answer is that there is no means of resolving from name
to IP address. On the other hand, I thought that the NetBIOS name could be
transmitted over TCP/IP. How can I make the pair of networks behave together
like one LAN and allow Windows Explorer on each machine see the hosts on the
other network?

One idea I had was to make all IP addresses static and resolve everything in
a hosts file, but I'm assuming there is a more elegant and easier way.

By the way, can one Windows WORKGROUP "span" both the 10.0.0 and the 10.0.1
networks?

Thanks and regards,

David

 

[John Wunderlich]

I have two small WORKGROUP networks, about 6 machines in each:
network 10.0.0.0/24 and 10.0.1.0/24 at different sites connected
by a VPN. Hosts on each network can see hosts on the other
network _only_ in terms of IP address. How can I allow the two
networks to see each other by host name? (Am I talking about
"NetBIOS name"?)

I suppose that the answer is that there is no means of resolving
from name to IP address. On the other hand, I thought that the
NetBIOS name could be transmitted over TCP/IP. How can I make the
pair of networks behave together like one LAN and allow Windows
Explorer on each machine see the hosts on the other network?

One idea I had was to make all IP addresses static and resolve
everything in a hosts file, but I'm assuming there is a more
elegant and easier way.

By the way, can one Windows WORKGROUP "span" both the 10.0.0 and
the 10.0.1 networks?

The problem is that Windows networking was never designed to cross
subnets. When you need them to cross subnets, then you need to set up
a WINS server. An alternate approach would be to enter all your
machines in the c:\Windows\System32\drivers\etc\lmhosts file (assuming
their IP addresses aren't dynamic).

I don't know what would happen if you opened-up the subnetting such
that both ends ended-up in the same subnet (e.g. 10.0.0.0/23)

HTH,
John

 

[David]

I have two small WORKGROUP networks, about 6 machines in each:
network 10.0.0.0/24 and 10.0.1.0/24 at different sites connected
by a VPN. Hosts on each network can see hosts on the other
network _only_ in terms of IP address. How can I allow the two
networks to see each other by host name? (Am I talking about
"NetBIOS name"?)

I suppose that the answer is that there is no means of resolving
from name to IP address. On the other hand, I thought that the
NetBIOS name could be transmitted over TCP/IP. How can I make the
pair of networks behave together like one LAN and allow Windows
Explorer on each machine see the hosts on the other network?

One idea I had was to make all IP addresses static and resolve
everything in a hosts file, but I'm assuming there is a more
elegant and easier way.

By the way, can one Windows WORKGROUP "span" both the 10.0.0 and
the 10.0.1 networks?

The problem is that Windows networking was never designed to cross
subnets. When you need them to cross subnets, then you need to set up
a WINS server. An alternate approach would be to enter all your
machines in the c:\Windows\System32\drivers\etc\lmhosts file (assuming
their IP addresses aren't dynamic).

I don't know what would happen if you opened-up the subnetting such
that both ends ended-up in the same subnet (e.g. 10.0.0.0/23)

HTH,
John
-----------
Thanks John,

First, both ends cannot be on the same subnet. A VPN is required to tunnel
between two _different_ networks.

Static IP addresses and resolution in hosts (not lmhosts) is too inelegant,
although it is easy to implement and simple to understand.

Therefore, if easy enough, I'll probably implement a WINS server. Is a
server version of Windows required for this or will Windows XP run a WINS
server? Furthermore, isn't running NetBIOS over TCP/IP sufficient in order
to notify all machines of the NetBIOS name for each IP address?

By the way, can a Windows WORKGROUP "span" two networks (10.0.0.0/24 and
10.0.1.0/24)?

Thanks again,

David

 

[John Wunderlich]

The problem is that Windows networking was never designed to cross
subnets. When you need them to cross subnets, then you need to
set up a WINS server. An alternate approach would be to enter all
your machines in the c:\Windows\System32\drivers\etc\lmhosts file
(assuming their IP addresses aren't dynamic).

I don't know what would happen if you opened-up the subnetting
such that both ends ended-up in the same subnet (e.g. 10.0.0.0/23)

HTH,
John
-----------
Thanks John,

First, both ends cannot be on the same subnet. A VPN is required
to tunnel between two _different_ networks.

Static IP addresses and resolution in hosts (not lmhosts) is too
inelegant, although it is easy to implement and simple to
understand.

Therefore, if easy enough, I'll probably implement a WINS server.
Is a server version of Windows required for this or will Windows
XP run a WINS server? Furthermore, isn't running NetBIOS over
TCP/IP sufficient in order to notify all machines of the NetBIOS
name for each IP address?

By the way, can a Windows WORKGROUP "span" two networks
(10.0.0.0/24 and 10.0.1.0/24)?

Yes, you would need a Server version of Windows to
implement a WINS server

Windows Networking relies heavily on Broadcasts to discover other
machines on the network and broadcast packets do not pass through
routers. On each subnet, a "Master Browser" is elected that keeps
track of all devices on its subnet then serves the list out to other
devices on that subnet that ask. WINS supplements that by gathering
lists from all the local Master Browsers, consolidates that list,
and sends it back to the Browse Masters to supply on demand.

For an overview of WINS, you might want to read:
<http://technet2.microsoft.com/Windo...becb-4965-848a-5db94df7698f1033.mspx?mfr=true>

As far as I can tell, there shouldn't be a problem spanning subnets
with a Workgroup.

HTH,
John