Nope, Adesk never really fessed up to any issues - other than to say that
with Novell Client32 installed things can get funky. I ran all the tweaks
at http://www.ithowto.com/novell/clientspeed.htm site to resolve my Netware
issues. The cursor hangs were the last of the problems, and once we could
verify that all devices were connected at the right speed/duplex settings
all was good.
All the client computers autonegotiate the speeds (all Compaq Evo units) and
will get the settings right. It was our Cisco routers that were not
correctly autonegotiating and had to be forced to the correct setups.
When the lags did hit, they went switch by switch in our setup - you could
hear people banging their mice around on the desks throughout the office.
It's like the work version of The Wave, it would start just outside my door
and travel counterclockwise until all the switches had been stepped through.
It worked from the bottom of the switch stack back up to the top - always
started at random times, but was consistent in that it moved 6-5-4-3-2-1
through the stack. Didn't seem to matter where in the stack the Cisco
routers were plugged in.
Mark Evinger
"wromberger" wrote in message
news:9561891.1093269215240.JavaMail.jive@jiveforum2.autodesk.com...
> Mark,
>
> Thank you for your reply. In your 2-year quest to track down your
hesistation issue did you ever have occasion to work with Autodesk towards a
solution? That is, do they have some history of this behavior?
>
> I've been down the connect speeds path, and have found that it makes a
profound difference if set incorrectly. More profound in fact than the mere
annoying hesistations that we are experiencing. We've tried forcing speed
settings but have found that auto-negotiation almost always connects at
100msp anyway and causes less problems than a forced mismatch.
>
> In your experience did you have users experiencing the lag, freeze,
hesistations, whatever we want to call it, all at the same time? And would
it just as suddenly clear up all at once?
>
> I'll pass along the "spanning-tree" protocol suggestion to my IT switch
guy.