Ascend Archive
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

RE: (ASCEND) 6.1.3, 4048, connections and disconnections (*Update*)




Thank you Jim Logan for the reply and the quick answer, it was right on 
target.

After talking with Ascend for close to an hour, it was determined that the 
4048 in question be cleared and reloaded.  After doing this , the 4048 has 
become stable.  I have not ran into the TCP/IP error messages since the 
fclear and then an NV and then tftp'ed the configuration back into the 
machine. To anyone out there who is somewhat new to the procedure of fclear 
and NV, please schedule downtime for this as it clears out your 
configuration and you must reload it back in. If done under a live 
environment, your callers will not be able to access the machine until you 
have reloaded the configuration.
The pool leak issue was also brought up and yes, I need to address a few 
more ip's in the pool.  Presently, we are assigining only enough to cover 
all the ports.  I have also made sure that Auth Pool = No as per you, 
others here in the group and Ascend.  It has since been around 12 hours and 
I have not heard a complaint, nor have I encountered the errors. It is now 
coming up in the magic hours of access and we will see how the box handles 
the callers.

Sincerely,

William
Intellistar Support Team



 Sounds exactly like the problem we were having (same Load and Version)
cause of the IP Pool Leak problem.. What happens (and you might check this
in terminal mode) is that the IP Pool gets totally depleted, esp if you do
allow MP/MPP callers, and 0 IP's are left.  In the dial-up users view, the
problem is reported (as you state) "Dial-up Networking Could not negotiate
a compatible set of protocols".  Since working with Ascend, and don't use
Ascend Radius - we use Merrit Radius - Ascend had us turn off Auth Pool=No
in the settings, and problem has not reappeared since.

>Ethernet >Mod Config >Auth >Auth Pool=No

The Default is Auth Pool=Yes

At 12:18 PM 7/28/98 -0400, you wrote:
>Yesterday I posted a message that stated we are having problems where
>random modem ports would answer and then prompt an error message from a
>WIN95 dialup screen.  At random, some of the ports will answer and then be 
>unable to negotiate TCP/IP handshaking.  When this happens, the PC's will
>response message is:
>
>"Dial-up Networking could not negotiate a compatible set of network
>protocols you specified in the server type settings. Check your network
>configuration in the control panel and the try the connection again"
>
>Most of you probably know,  that message is usually because TCP/IP is not
>configured or incorrectly configured on the PC. But in this case, if you
>dial in again, you may get connected.  This is causing havoc on our 
network
>as users are either calling for tech support or are changing their 
settings
>thinking that the problem exists on their end.
>
>I have started the documentation and testing of this, with the two PC's
>running Win95 and USR modems. Here's what I have found so far:
>1)After a reboot, it may take as much as 12 hours for these problems to
>crop up.
>2)The ports that it affects are random, but I seem to have more of the
>errors on the second modem card.
>3)The modem ports that go down , will stay down until you reboot, but will 
>still accept calls and start giving the negotiation errors.
>5)I am watching my hair gray as this happens (joke!)
>
>LQM is turned off and stacking is on, it dosen't seem to be affecting the
>other 4048 in the group, but they are not the first in the dialup 
rollover.
>After a reboot, the problems magically seems to disappear until later. Our 
>version of upgrade was only(6.1.3) ftik.m40 which is not too elaborate in
>any since of the word.  Most of you are probably running way more than
>this.
>-----------------------------
>My theory
>I believe the modem ports are getting confused out there somehow and that
>they just seem to start behaving erratically. It seems that the 
negotiation
>protocols for v.90 are confusing them possibly.
>-------------------------------
>If anyone is having similar problems or has any solutions, please feel 
free
>to post or e-mail me as I follow this group closely.  I realize that 6.1.3 
>has had its share of complaints, but there has got to be some resolution 
to
>this that I am probably missing in learing these machines.  I welcome any
>an all responses.
>
>Sincerely,
>------------------------------------------------------------------------
>---------------------------------------
>William Roberts				/	IntelliSTAR
>Intellistar Network Administrator		/	www.intellistar.net
>willr@intellistar.net			/	Full Service Provider	
>------------------------------------------------------------------------
>---------------------------------------
>
>++ Ascend Users Mailing List ++
>To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
>To get FAQ'd:	<http://www.nealis.net/ascend/faq>
>
>
***** Top Net InterNet Services *****
Omaha, Nebraska         Husker Heaven
www.top.net            (402) 291-1542
 Visit Our BBS at: www.hawgwild.com

++ Ascend Users Mailing List ++
To unsubscribe:	send unsubscribe to ascend-users-request@bungi.com
To get FAQ'd:	<http://www.nealis.net/ascend/faq>