Novell Frame Types

[Francis]

Having bother with a rebuild for a customer. Clean 2000 install, then installing Client 32 v4.91, server is 4.11.
Network is IP preferred with IPX as well, static IP's, subnet mask and GW. Definitely has the right tree, context and server details and I've matched the settings page by page with a working machine, everything is identical, but it always defaults to 802.2 frame type when the server is 802.3 (clients are set to auto frame detection). Been told not to set the frame type manually as it will cause more bother in the long run, there's no in house IT,that's from someone in our place that knows the site and should know exactly what he's talking about.
Before I left, I tried without NMAS as apparently it can stop the server and client autonegotiating, also tried installing IP with IPX compatibility as opposed to just IP + IPX. At one point while working logged into the workstation it did change the frame to 802.3 and did ind the tree, one reboot later and I'm back to square 1 :cry:
Any ideas :shrug:

[Francis]

Quick bump on the off-chance I can get something for tomorrow ;)

[ffc]

I always thought the IP frame type was Ethernet_II and IPX used 802.3 by default. I am dragging my non too efficient long term memory though.

[Francis]

I always thought the IP frame type was Ethernet_II and IPX used 802.3 by default. I am dragging my non too efficient long term memory though.
Ethernet II can support IPX/SPX, TCP/IP and Appletalk(?), 802.2 can support IPX/SPX and something else, 802.3 is IPX/SPX only. This netware 4.11 server uses 802.3 and all the other clients are autodetecting this and communicating happily, the rebuilt PC is not autodetecting and defaulting to 802.2.
Messed around with it earlier and it does run if forced to 802.3, but found out they have a proprietary app that doesn't work unless it's set to auto for reasons beyond me.
No urgent rush with it now, so it's been left till I can free up time to go back and look at it properly.

[sjg1]

Not a chance of anything NMAS-related working when your server is NW4.11! The 4.8x and 4.9x clients are maintained as separate lines - the recommendation is that if you're in a NW5.1 or earlier environment, go with 4.8, if you're on the later stuff go with 4.9. You can get a few wierd problems otherwise as client components are looking for things running on the network that just don't exist.

"IP with IPX compatability" is used when you're running an IP backbone but have apps that need to communicate using IPX - effectively you're running IPX encapsulated over IP. Not what you want really in a 4.11 environment. IP+IPX is what you want.

The recommendation I used to hear from CNEs years ago was to stick with 802.2 everywhere. There is some good reason for that, but it's escaped my memory - we moved away from IPX a fair while ago.

[Francis]

So downgrade the client to 4.8?
Didn't know a thing about the seperate lines, will have to email that to myself so I've got it somewhere ;)
Only thing is that there is a definite 4.91 client running (it's one I installed ages ago). Went throught setup as IP+IPX and didn't change anything else so I'd assume the NMAS and NICI installed, and it works fine. Same process and settings on this one, even reinstalling with/without NMAS and NICI, just never works.

Can't find 4.8x available on Novell, but have found them elsewhere, any of the 4.8x series do? Also appears to be a sp1 and sp2 for 4.83, most recent be OK?