Delay at startup

[sinc]

Any idea what could be causing this?

Our office switched to a gigabit ethernet from a pitifully slow wireless network. The only thing that changed is that I installed a gigabit ethernet card, and switched my network to use it instead of the wireless NIC. Now, every time I start Autocad, there's a 10-second or so pause after a drawing loads and just before the express tools initialize. If I disconnect the network cable, this delay goes away. This problem did not exist before.

I made absolutely no changes to Autocad files, configuration, my directory structure, or anything else. All I did was switch networks on the machine. Autocad has never (to my knowledge) been configured to get anything from any remote computer, and that is still the case, so as best I know, it should not be trying to access either the new network or the now-missing wireless network for anything that I'm aware of. As of now, drawings and projects still are on the local machine in the same place they've always been, not on another computer in the network. In addition, all computers that were available before are still available, same with printers, etc., but as I said, Autocad should have no reason to look for anything except maybe printers.

[Mike.Perry]

Hi

Have a browse of the following threads (hopefully will give you one or two things to look at) -

2004 Lags

Problem with open/save dialog box

+

<add>
Have you tried searching the Forums (Network / Delay / Slow / Startup / etc), there is quite a bit of information available on this subject -

Search Forums
</add>

Have a good one, Mike

[sinc]

Thanks for the pointer. We have a small office, with four computers on a simple peer-to-peer network. I had gone through all our computers, moving them all one at a time to the new wired network from the too-slow wireless network, while leaving them on the same Windows network through the procedure (which happened to have the default name MSHOME). This seemed to confuse Windows, and at the end, none of my computers had permission to access MSHOME in Network Neighborhood, even though file and printer sharing were still working. Creating a brand new Windows network with a new name and abandoning the corrupted MSHOME network solved the problem.