NetBIOS Problem

  • Thread starter Thread starter Daniel Rudy
  • Start date Start date
D

Daniel Rudy

Hello,

I have multiple WinXP and a couple of Win98 machines on a network. The
network is segmented into two different subnets. The problem is that
machines on one subnet cannot talk to machines on the other, this includes
NetBIOS enabled printers.


10.0.0.0/24
|
|
Router ----- Internet
|
|
10.0.1.0/24

The machines on 10.0.0.0 can talk to each other, but they cannot talk to the
machines on 10.0.1.0. Although, you can ping the individual machines across
the subnets, which tells me that I do have IP connectivity. Also, machines
from both subnets are able to access the internet. The machines on the
10.0.1.0/24 network are wireless and as such, that subnet does not have any
printers. The printers are on the 10.0.0.0/24 network, and the wireless PCs
need access to them.

What is going on? What can I do about it?
 
"Daniel Rudy" said:
Hello,

I have multiple WinXP and a couple of Win98 machines on a network. The
network is segmented into two different subnets. The problem is that
machines on one subnet cannot talk to machines on the other, this includes
NetBIOS enabled printers.


10.0.0.0/24
|
|
Router ----- Internet
|
|
10.0.1.0/24

The machines on 10.0.0.0 can talk to each other, but they cannot talk to the
machines on 10.0.1.0. Although, you can ping the individual machines across
the subnets, which tells me that I do have IP connectivity. Also, machines
from both subnets are able to access the internet. The machines on the
10.0.1.0/24 network are wireless and as such, that subnet does not have any
printers. The printers are on the 10.0.0.0/24 network, and the wireless PCs
need access to them.

What is going on? What can I do about it?
Click to expand...

NetBIOS name resolution in a Windows 98/XP network with multiple
subnets requires an LMHOSTS file on each computer. That file defines
the name-to-IP mappings for computers on the other subnet.

Even with LMHOSTS, you won't be able to browse across subnets in
Network Neighborhood and My Network Places.

You should be able to access a computer in the other subnet, without
name resolution, by typing the other computer's IP address in the
Start | Run box in this form:

\\10.0.x.x
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
GTS said:
If you want the machines to talk to each other, then why are you creating
separate subnets?
--
Click to expand...

It was done that way to create a physical partition between wired and
wireless clients. The resoning behind this policy decision is if there is
an intruder on the wireless side of the network (which has happened before),
then the different network segments can be easily isolated to stop an
intruder in their tracks. I didn't make the decision, but it makes sense
when you think about it as one commnd on the router will drop the interface
which all wireless traffic flows though.
 
Steve Winograd said:
NetBIOS name resolution in a Windows 98/XP network with multiple
subnets requires an LMHOSTS file on each computer. That file defines
the name-to-IP mappings for computers on the other subnet.

Even with LMHOSTS, you won't be able to browse across subnets in
Network Neighborhood and My Network Places.

You should be able to access a computer in the other subnet, without
name resolution, by typing the other computer's IP address in the
Start | Run box in this form:

\\10.0.x.x
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
Click to expand...

I got it working.

Since the router is a Unix box (FreeBSD), I installed Samba and configured
it as a WINS server. Now everyone can see each other though the Network
Neighborhood/My Network Places browser...including printers.
 
"Daniel Rudy" said:
I got it working.

Since the router is a Unix box (FreeBSD), I installed Samba and configured
it as a WINS server. Now everyone can see each other though the Network
Neighborhood/My Network Places browser...including printers.
Click to expand...

That works, too. :-)
--
Best Wishes,
Steve Winograd, MS-MVP (Windows Networking)

Please post any reply as a follow-up message in the news group
for everyone to see. I'm sorry, but I don't answer questions
addressed directly to me in E-mail or news groups.

Microsoft Most Valuable Professional Program
http://mvp.support.microsoft.com
 
Daniel Rudy said:
It was done that way to create a physical partition between wired and
wireless clients. The resoning behind this policy decision is if there is
an intruder on the wireless side of the network (which has happened
before),
then the different network segments can be easily isolated to stop an
intruder in their tracks. I didn't make the decision, but it makes sense
when you think about it as one commnd on the router will drop the
interface
which all wireless traffic flows though.
Click to expand...
Gotcha. Not a bad idea.
 
Back
Top