Sign up on the Revelation Software website to have access to the most current content, and to be able to ask questions and get answers from the Revelation community

At 22 APR 2003 12:34:05PM Matt Sorrell wrote:

We have a remote user that we are trying to get connected to HR-1 back here at our corporate office.

We are running NetWare 5 with the NLM. I cannot remember the exact error number she is receiving, but it is one of the ubiquitous "unable to open boot media map" errors. There is SAP filtering in place, but we are allowing the NLM SAP to be broadcast.

However, one of the networking guys just told me today that the interface on the Cisco router is set up for 802.3, while our server and all of the clients are set up for ETHERNET_II. Could this be the cause of our problem?

I remember at the time thinking that the FS error she was receiving was the same one that local clients got when their frame type was set wrong, but the frame type is configured correctly on the her machine.

My last guess at this point is that the router, because it is not configed for ETHERNET_II, is causing the problem similar to when a client is misconfigured on frame types. I just want to make sure this is not a red herring before I have the networking guys start changing the config on the router.

Also, on a tangentially related note, she cannot browse the Novell network. If I open a DOS prompt and have her issue a NET USE command, she can map to the Novell server, but if she tries to map through the GUI, she receives an error message. Once the drive is mapped, she can navigate to and through it via DOS, but Windows Explorer doesn't show the drive. Could this also be related to the frame type setting on the router?

Thanks!!

[email protected]

Greyhound Lines, Inc.


At 22 APR 2003 12:59PM Don Miller - C3 Inc. wrote:

Matt ..

Yes on all counts, I think. The router should be configured to allow for 802.2, 802.3, ETHERNET II (and maybe ETHERNET SNAP). I would also configure the server to support all clients as well. Unless it's a really slow server, it shouldn't be any kind of serious performance hit. The desktops should be set to a "preferred" frame type (not AUTO). If you don't want to fiddle with the Cisco router, you might get away with just installing all the frame types on the Netware server.

Don M.


At 22 APR 2003 02:07PM Matt Sorrell wrote:

Don,

Thanks for the response. Just about the only thing we run IPX for anymore is our ARev app. All of our NetWare servers are running in IP-Only mode except for our two ARev servers, which run in mixed mode.

The decision was made to configure them just for ETHERNET_II. I believe that decision was made back when we were running IPX for a number of things.

The way our environment is set up, it will actually be easier to change the config on this router instead of having to mess with the server.

Again, thanks for the response. I will post a follow-up tomorrow to document whether or not this actually works.

[email protected]

Greyhound Lines, Inc.


At 23 APR 2003 10:30AM Matt Sorrell wrote:

Well, it's official.

If the ethernet interface on the router isn't configured for the proper frame type/encapsulation, nothing works. Imagine that.

Thanks for the help, it is greatly appreciated.

[email protected]

Greyhound Lines, Inc.

View this thread on the forum...

  • third_party_content/community/commentary/forums_nonworks/af0366268e1170b485256d10005b0313.txt
  • Last modified: 2023/12/28 07:40
  • by 127.0.0.1