Networks

Ask something
Discussion Locked

Login Problems

0 helpful
12 replies

by mark

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
I helped someone clear an error message from a Novell 3.1 Server where it kept beeping and saying that Router...says network should be 1 not 2, etc., by changing the NET= line in the autoexec. The errors quit, but a couple days later he called to say he now has another problem. Users can't login because there are too many users. He has a 5 user license and only 3 users, but he is connected to a much bigger network. The monitor shows only users. He can clear the connections and then the users can get in, but this is very annoying to say the least. The alarms are also annoying if we put it back like it was. Any suggestions?

12 replies

by tbradley

For starters, put it back, then turn the alarm bell off via the monitor program under server parameters. The error will still be there, but will not be audible.

The users are not taking up a license, so the problem has to lie in server resources. 3.12 can support a limited number of active connections, ( not actual logins ). Don't know what exact version of 3.1 and patch level, but you can try IPXCON to see if you can bump those values up.

Up to the point where you changed the net number, the other servers in the network were rejecting the 3.1 server, so workstation requests were not routed to it.

When the workstations in the rest of the Network were "blocked", they were not sending a connection request to the 3.1 server, but now that you've made it one of the "good guys", you're going to have to do quite a bit of client side configuration to turn off bindery connections.

Much easier to turn the alarm bell off, leave sleeping dogs lie, and turn the monitor off so the error messages aren't visible.

What does the rest of the network consist of?
NW4, NW5, NT? If all other users are on 4 or 5, a global client update using ACU could solve the problem.

When did the problem start? Was the 3.1 standalone up until a certain point, or was another piece of equipment added to the network that started the problem?

by tbradley

Answer number 3 stirred up some foggy memories of 3.12 nightmares, and the problem could very well lie in your network printers

( this is pre - changing the net= line )

Simply re-set all the printers, and turn off IPX in the config. With HP printers, this is easy, simply use a web browser to access the printers assigned tcp/ip address. Other brands? well... I guess that's why they still ship manuals.

When you said the network was all tcp/ip other than the 3.1 server, I would assume that printing is also tcp/ip. If you've got some NW boxes out there that still use IPX based print queue/print server, this won't fix the problem.

But back to the simplest part of the problem. If as you've said, there is only 5 users, the chancesof a serious problem happening with the 3.1 server is a much less probable situation than "tweaking" the rest of the network and possibly causing some severe havoc.

by mark

Poked at the problem, but didn't give the solution that the NLM patch does. Thanks for taking time to respond.

by mark

I don't like the idea of turning the alarm off because he may get more serious alarms that needs attention. He mostly has NT servers on the rest of the Network and I suggested he remove Netware Clients from the offending PCs, but since he is on a WAN and there are alot of PCs and locations involved, he wasn't keen on that idea. I think I will find out if he has the 3.2 enhancment pack loaded and if not try that. I've never seen one recognize as a connection. That may fix it. If not, maybe he can turn off IPX routing on his router since I think he only needs TCP/IP on the WAN. I'll also look at your IPXCON suggestion. I'm not familiar with that setting.

by stephen_sykes

Agree with above, put the NET back as it was. make a note of the MAC address of the "router" causing the problem and track it down. Turn it off - does the problem go away ? This could be something as simple as a printer being moved from one network to the other but still advertising the fact it was on network 1 to begin with !

by jackie d.t.

Hi Mark,

NW 3.x servers should run NLICLEAR.NLM, which will clear unnecessary "Not Logged In connections" dynamically. This file is provided in the current OS patch kit (312ptd.exe at the time of writing), but must be copied and loaded manually.
Warning: The "Net=" stands for, it is the "external net number" which is the "broadcast address" of the cable segment you are on. You don't randomly change this.

The NLIClear.NLM works great.
Hope this helps,
Jackie

by jackie d.t.

Very Important: When you get messages on the Server that "the Router...says network should be 1 not 2, etc." check to see if it is your server complaining or if the message is comming from another machine. The message gives the NIC MAC address with the message. If the message is comming from a server which is on another cable segment, it may be an erroneous message. There should be no reason to change the address unless it the server was moved to a different cable segment.

by mark

The problem started when this LAN was connected to the Adjacent LAN and WAN via a HUB. I had seen this problem before and always just changed the NET= line to match, thereby putting both networks on the same LAN. I just never ran into this login problem before. Looks like some others have and I think you provided the NLM patch I was looking for. If it doesn't work, I'll email you back. Thanks.

This discussion is closed to new replies.