Question : Novell, Netware, 6.5 sp6 latency issues

I just upgraded our Netware server from sp3 to sp6 last night.  Didn't really detect an issues initially after the upgrade.  I installed the manadatory cifs and edirectory updates and the recommended tcp update.  I'm pinging the inside address of the server and occassionally notice some really high latency times...ranging from 1000-2500ms for about 10-15 seconds and then it goes back down to under 1ms.

The server is running as a file server, Groupwise, Intranet (php and mysql), and is running arcserve.  It's used by about 25 people inside the office and externally by about 25 people via ssl vpn.

Any idea what would cause the latency and how i can determine where it's coming from?

Answer : Novell, Netware, 6.5 sp6 latency issues

Sorry, but I only have NetWare 6.0 available to me at the moment.  I don't have that reg key shown in TID 10100621.

However, if the "ip management page with all the protocols" is the same as what I think it is, it's likely that a lot of things "set to 0.0.0.0" are actually protocol ports that are listening for "all addresses."

Some things with IP actually have to be set to "0.0.0.0" - that's the "default route," for example.  

If you look at "protocol information" and "IP," near the bottom (on mine anyway) I show an IP Address table section that has the IP address(es) bound to my NIC(s), an "IP Address Translation Table" section that shows the ARP table known to the server's router, and an "ip routing table" showing the route configuration, with the default route being the one with a 0.0.0.0 destination address.

If you go to "protocol information" and "TCP" however, it will show all of the TCP listening ports/connections in the "TCP Connections Table" section.

You'll see that a number of those "listening" connections will have a 0.0.0.0 address in both the "local" column and "remote" column.  That's normal, depending on the port.  Other "listening" ports only have 0.0.0.0 in the "remote" column.  Also normal.

However, if you have the exact situation as described in the TID, with your SSL key following 0.0.0.0 in your registry, then that's not normal - but only applies to NW6.5, apparently, not NW6.0.

Hope that helps.