Go Premium for a chance to win a PS4. Enter to Win

x
?
Solved

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

Posted on 1997-06-03
5
Medium Priority
?
282 Views
Last Modified: 2011-09-20
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
0
Comment
Question by:asz
  • 2
  • 2
5 Comments
 
LVL 1

Accepted Solution

by:
MikeCrist earned 200 total points
ID: 1584767
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
 

Expert Comment

by:egorov
ID: 1584768
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
 

Author Comment

by:asz
ID: 1584769
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
 
LVL 1

Expert Comment

by:MikeCrist
ID: 1584770
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
 

Author Comment

by:asz
ID: 1584771
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

Featured Post

VIDEO: THE CONCERTO CLOUD FOR HEALTHCARE

Modern healthcare requires a modern cloud. View this brief video to understand how the Concerto Cloud for Healthcare can help your organization.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

I have seen several blogs and forum entries elsewhere state that because NTFS volumes do not support linux ownership or permissions, they cannot be used for anonymous ftp upload through the vsftpd program.   IT can be done and here's how to get i…
Note: for this to work properly you need to use a Cross-Over network cable. 1. Connect both servers S1 and S2 on the second network slots respectively. Note that you can use the 1st slots but usually these would be occupied by the Service Provide…
If you're a developer or IT admin, you’re probably tasked with managing multiple websites, servers, applications, and levels of security on a daily basis. While this can be extremely time consuming, it can also be frustrating when systems aren't wor…
Despite its rising prevalence in the business world, "the cloud" is still misunderstood. Some companies still believe common misconceptions about lack of security in cloud solutions and many misuses of cloud storage options still occur every day. …

783 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question