Discussion Locked

Netbios on ipx/spx required ?

0 helpful
4 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

NT 4 server, protocol is ipx/spx, frame 802.2 and netbios.

Workstation is Win98 FE, protocol is ipx/spx, frame 802.2

Seems I can only see the NT server if I add Netbios over ipx/spx on the Win98 machine. Is this correct operation ?

I seem to remember doing this before without requiring Netbios, that might have been a Win98 network though.

Any ideas ?

I also have specified different internal network numbers for the 802.2 frame type, to ensure its unique.

Les

4 replies

by quahsays

it's interesting that you are using ipx/spx for NT, and i thought this protocol is for Netware?
NetBIOS is used when the network is not using TCP protocol, NetBIOS is required if you want to support standard Microsoft network (computer) browsing.
you typically only use ipx when you have a Netware NOS.
Between Windows systems, you would require TCP and NetBIOS (may need WINS Server)

by curlergirl

Yes, you do need NetBIOS over IPX under these circumstances. You might be thinking about a situation where you were running IPX/SPX with a Novell network - this doesn't require NetBIOS, but Microsoft networking does. Why are you using IPX/SPX instead of TCP/IP? Just wondering. . .Hope this helps!

by @lberto

You have a configuration problem, first of all, Novell Netware was the one that needed to use IPX/SPX only on versions prior 4.X, since they release 4.X you can bind TCP/IP over your NIC. Anyway, if you are using Windows NT 4.0 I suggest you to use TCP/IP, is more reliable, faster, safer.
If you are using another server (Novell) on the same network then you should use IPX/SPX, I suggest you to purchase Novell Client, install it on your workstations and you won't have problems anymore, it will also fix some little bugs that Win98 has when working with Novell.
On small words, make sure your server is running TCP/IP and forget about IPX/SPX for NT.
Best Regards,
@lberto

by lelton

I *WANT* to run ipx with NT ! Client32 is used to access our Netware resources using ipx.
Please note tcp/ip came with netware 4.x BUT can only used for routing other resources that use tcp/ip (like Unix), you CAN NOT login to a Netware 4.X server with tcp/ip. This is part of the CNE exam.

You can though with Netware 5.X, which is where the confusion might be.

It seems that Win98 has a protocol priority problem when I am running MS client stuff with tcp/ip or ipx with netBIOS added. That problem seems to go away when I am just using bare ipx and tcp/ip is not bound to the MS client for MS networks.

This is why I want to use ipx on the NT resources to solve this problem.

I have heard there are some registry hacks to force the protocol priorty to always use the Netware client with ipx first, then the MS client with whatever its bound to second, I just don't know where to find this.

This is really really easy on NT workstation (or server) just by moving the protocol/client higher on the NT protocol stack list, but we don't have such an easy facility under Win98.

Les

This discussion is closed to new replies.