Two workgroups with Novell--Linux bridges between them Win95 clients from Workgroup1 don't see Workgroup2 in theirs Network neibourhood, and vice versa

When I've got this conviguration...
      Workgroup1: Win95 clients
      Novell server [bridge] ... another Novell server[bridge]
      Workgroup2: Win95 clients
....In Network Neibourhood there were TWO Workrgoups, Workgroup1 &
Workgroup2...

And now, when I have this configuration...
      Workgroup1: Win95 clients
      Novell server [bridge] ... Linux server[bridge]
      Workgroup2: Win95 clients

....In Network Neibourhood clients from Workgroup1 seen 'Workgroup1' and,
respectively Workgroup2 see ONLY 'Workgroup2'.

The problem is: Workgroup2 disappeared from Network Neibourhood of
Workgroup1 clients, and, respectively, _.
But if I look into StartMenu|Find|Computer I see ALL clients, from BOTH
workgroups.

Client Win95:
      IPX
      NetBIOS over IPX
      TCP/IP
Novell bridge:
      IPX
      TCP/IP
Linux bridge:
      Samba 1.9.16p11
      NCPFS
      IPXRIPD
aszAsked:
Who is Participating?

[Webinar] Streamline your web hosting managementRegister Today

x
 
MikeCristConnect With a Mentor Commented:
Instead of having the linux box configured as a true bridge, you have it configured as a router (from what it sounds like).  Basically, you have to transparently bridge the two, without having the Linux box show up.  NetBIOS (What Win95 uses to discover other windows boxes) won't pass routers.  Neither will NetBEUI (unless you encapsulate them, you have to setup Linux to route or bridge IPX).

Hope this helps.
0
 
egorovCommented:
As far as I know, Win95 does like that: when somebody clicks on a "network neighborhood" icon, it begins to listen to all servers via SAP protocol. If some hosts will fail (no answer in timeout) they will not be displayed in network neighborhood window.
But when you try to find a computer via "Start" menu, there is much bigger timeout so  you can see this host.

0
 
aszAuthor Commented:
If instead of Linux box in previously described configuration I temporarily
place Novell, then on NwlnkNb protocol I CAN communicate with workgroup1's master browser.

But when I use Linux - can not :(

Routing on Linux box configured OK & with Novell server I CAN communitcate with
IPX protocol.

0
 
MikeCristCommented:
NwlnkNb is NetBIOS encapsulation in IPX.  Therefore, the NetBIOS win95 uses is passed fine.  Thats why you can see them.

What you have to have the Linux box do is encapsulate the NetBIOS, pass it through the router, then strip the IPX off the NetBIOS packet.  Novell does this by default, it encapsulates everything in IPX (except IPX) and then passes it through the router, then strips the IPX headers off.
0
 
aszAuthor Commented:
How do I understand things in case of Novell:

Win95 client created NetBIOS packet, incapsulated it into IPX packet (NwlnkNb) the result came to Novell box - it stripped the IPX off the NetBIOS packet, created(incapsulated) NEW IPX packed from that, and sent the resulting packet to another subnet

How do I understand things in case of Linux:

Win95 client created NetBIOS packet, incapsulated it into IPX packet (NwlnkNb) the result came to Linux box - it stripped the IPX off the NetBIOS packet, took a look inside, and decided, that there's some garbage (our precious NetBIOS packet)
and wouldn't process it further [just ignored]

1. Correct me if I misunderstood something.
2. What steps should I take, to fix that thing?
3. What books could you recommend me on the subject?

0
All Courses

From novice to tech pro — start learning today.