On Mon, 16 Aug 1999, Ken Kirchner wrote:
uh, what? We have also had ISDN issues since our last upgrade. I have a NetGear RT-328 at the house, and while I cant make it lock up on demand, if my roomate and I pound on it for a half-hour or so with two simultaneous sessions of "Half-Life TFC" it will usually happen. I am bringing home a modem so I can log in and see whats happened to the session tonight.
I have not seen this problem nor have heard from anyone - A few days ago I came to know about this - may be I missed this list or something. As far as ISDN goes - I used it - have a nailedup connection with our chassis here and have never seen the problem - I do use some of the same TA's mentioned in the problem.
2. The versions of code: HiPer DSP: 1.2.59, HiPer ARC: 4.1.59, NMC:5.5.5
I would suggest the latest DSP code, 1.2.59 DSP code is really old and had some issues - you need the latest 2.0.x code.
We are using:
HDM: 2.0.81 ARC: 4.1.59-6 NMC: 6.2.17
So I doubt 2.0.81 will help. The main reason we jumped to 2.0.81 was because 1.2.37 caused authentication problems with our Mac users. Fix one thing, break another. :)
Got to disagree with this. 2.0.81 has more fixes in terms of packet bus issues and features. Yes 1.2.37 is very close but does not have the same type of feature set.
3. I understand these problems can take time to fix, I am just frustrated with the 3Com responses through last Thursday evening. The response from Krish was the first real help I've gotten.
Well, thankfully Krish is here now. I hope we can give him something to work with.
4. We have implemented the MTU change. If Krish can contact me (850-337-016), we have a locked up system right now.
We have not tried the MTU option. I want to make sure it's not my Netgear first. Don't get me wrong, we have a lot of ISDN customers complaining, but I've had compression turned on recently, and now that it's off, I want to make sure that isnt what was choking the router. The router, when first recieved and brought on-line (around September of last year) worked flawlessly (with out compression) until 2.0.81. AFAIK it was screwing up before I played with compression.
Krish, what commands would be most beneficial for me to run for your troubleshooting efforts? (from the ARC or HDM? Both?)
So the problem is there irrespective of compression enabled or not correct? If so are you also have the same problem where you cannot browse (send http data) but can use pings etc? If that is the case first in order to reproduce the problem faster I would recommend setting the mtu for the user at a low value like 576 and then disable tcp header compression. If you have a setup where the problem is currently happening send me note, will be glad to take a look at it. krish
___ ___ (___) Kenneth Kirchner .o. mailto:kenk@shreve.net (___) (__) Asst SysAdmin .o. Voice (318) 222-2638 Ext 108 (__) (_) ShreveNet, Inc. .o. Fax (318) 213-6612 (_)
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.
- To unsubscribe to usr-tc, send an email to "majordomo@xmission.com" with "unsubscribe usr-tc" in the body of the message. For information on digests or retrieving files and old messages send "help" to the same address. Do not use quotes in your message.