Okay, I am at my wit's end.

We are running HR-1 (ARev 3.02) on a Novell 5.x server using the appropriate NLM. On our Win95 and Win98 desktops, it is stable as can be expected, and runs quite nicely.

Recently, we have been trying to get it working on WinXP Professional desktops. I have gone through all of the normal configurations that I can think of. I have set IPX as the preferred protocol (instead of IP), ensured that it is bound to the correct frame type (ETHERNET_II), and verified that the user has the NLM installed and loading (thanks to a batch file).

However, on every machine I try this on, I receive FS461 errors. As I mentioned, it is a WinXP Professional machine, with the 4.93 Novell client loaded. I was originally getting FS472 errors, but fixed that with the frame type binding. I cannot get past this 461 error.

If anyone has any ideas, they would be greatly appreciated.

TIA!!!

[email protected]

Greyhound Lines, Inc.

Matt,

ETHERNET_II is a hybrid protocol. If (for testing purposes) you alter to 802.2 do you get any joy?

Steve

Steve,

I will try that on Monday (been out of the office for several days.)

I will try it on the client and see what happens. I know the server is set to ETHERNET_II, and my understanding was that the server and client needed to be running the same protocols. If I have to change it on the server, it will be a pain due to the distributed nature of our user base.

Thanks for the info, though. I will report back with results shortly.

[email protected]

Greyhound Lines, Inc.

Silly key. *sheesh*

Okay, here's the question. I was talking with our network guys, and they had some questions. Keeping in mind that we have a switched network, with two different buildings involved (connected by a DS-3 along with backup T-1s), there are a number of routers and switches along with the server and client desktops in the mix.

The question is, where exactly do we need to make the change to 802.2? Does it need to happen on the client, the server, or both? The reason for the questions is that our routers are only configured with ETHERNET_II encapsulation. In order for the 802.2 to work, we have to add that as another encapsulation on the routers. So, is it enough to change the client to 802.2, and add that as an encapsulation on the router? The thought of our network guru is that as long as the router is talking 802.2, it will handle the hand-off of an 802.2 packet from the client to the server running ETHERNET_II. I have to admit, some of this is over my head and I don't understand all of the in's and out's of network routing.

Any additional info or thoughts you could share would be appreciated.

Thanks!!

[email protected]

Greyhound Lines, Inc.

View this thread on the forum...