Computer peeps..Server 2003 question..

G-Rex · 12-05-2008, 08:21 AM

Ok, so I just connected a new Windows 2003 Server, accessing it with Windows XP Pro and Windows 2000 Pro.

I don't have the whole thing online totally yet, as the old NT server is still running, because of a problem I am having.

The main job of the server is file storage. I do have it set up as a PDC, with DNS and DHCP configured.

The problem I am having is file access. When I try to open an AutoCAD file, the system practically locks up. It drags to the point that it tells me the file is invalid. I can copy the same file to my hard drive and it opens quickly and perfect. No troubles.

The cabling is not in question. Connectivity is fine. Even Word and Excel drag a little bit, but at least they open. Although, if i open Explorer and try to double click on the file there, it will lock the system up too. I'm at my wits end and any suggestions would be very welcomed!

I'm going to call Dell this morning and hope that I talk to someone I can understand. I haven't had such good luck with that in the past.

Papa_Complex · 12-05-2008, 08:29 AM

It might help the server types if you can say how you're accessing it. Are you using UNC pathnames? Drive mappings? Are there any UNC pathnames or drive mappings that have recently been eliminated? This can result in long delays, while Windows decides whether the dead links are still valid. If you have the "Web Client" service enabled on the XP box (it is by default), then XP will look for web content on any folder that it tries to open. This also slows things down. Then there's the way that Windows looks for Scheduled tasks on every remote folder. I don't have the registry hack handy, but it's one entry that needs to be changed, in order to disable this.

*EDIT* I did a quick search and found that system time settings can also cause issues with remote access speed. Have you matched the time zone on the 2003 server to your location and are both systems time synchronized (or at least close)?

G-Rex · 12-05-2008, 08:46 AM

I've tried accessing both ways Rob. Right now, I have a netlogon.bat file setting drive mappings prior to user login. Everything is current and fresh. I don't know if Web Client services are enabled. If it is by default, then it probably is, as the XP boxes are new also.

There's also a line in the netlogon.bat file to synchronize server and desktop times. I hope this helps to start. I spent ALL day yesterday messing with it, as well as a good friend of mine was logged in from home helping me with it. He's confused too, and he has a couple hundred 2003 Servers deployed at his company.

Help!

Quote:

Originally Posted by Papa_Complex

It might help the server types if you can say how you're accessing it. Are you using UNC pathnames? Drive mappings? Are there any UNC pathnames or drive mappings that have recently been eliminated? This can result in long delays, while Windows decides whether the dead links are still valid. If you have the "Web Client" service enabled on the XP box (it is by default), then XP will look for web content on any folder that it tries to open. This also slows things down. Then there's the way that Windows looks for Scheduled tasks on every remote folder. I don't have the registry hack handy, but it's one entry that needs to be changed, in order to disable this.

*EDIT* I did a quick search and found that system time settings can also cause issues with remote access speed. Have you matched the time zone on the 2003 server to your location and are both systems time synchronized (or at least close)?

Papa_Complex · 12-05-2008, 09:10 AM

It's worth manually checking the date, time, and time zone settings on both boxes, just to be safe. As I've frequently found over the last 20 years of desktop support, just because something SHOULD happen, that doesn't mean that it DOES

You would be best off removing the NT box from the network while testing this, so obviously this will have to be done at a time when production isn't necessary.

It's easy to disable Web Client on the XP box. If that doesn't help, then you can always re-enable it later. Go into Control Panel and set it to "classic view", then call up Administrative Tools, then services. Scroll down toward the bottom and find Web Client. Double click it, stop the service, then set it to disabled. Reboot and try again.

Clear the "recent documents" list from the XP box. Make sure that there are no links in My Network Places that point to resources that no longer exist. Turn off the antivirus, or uninstall it completely. See if you can access the shares faster via IP address than by name (I've seen this more than a few times).

I looked around and found the registry entry for Scheduled Task searches on remote computers. It's in this location in the registry, on the XP box:

HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Explorer\RemoteComputer\NameSpace\{D627 7990-4C6A-11CF-8D87-00AA0060F5BF}

First export it so that you can restore it later, if you want to. After that, delete that registry entry and reboot. There's another entry in the same group for printer searches that can be deleted too, with the same recommendation to back it up first. This used to be a HUGE speed issue here, when we had a mixed Windows/Novell server environment.

*Another EDIT* I forgot to ask what service pack level the server was at.

G-Rex · 12-05-2008, 09:39 AM

Ok Rob, I verified the time stamp is the same on both system.

I also disabled Web Services on my XP system, and deleted the two registry keys you suggested.

I am still having the problem. Although now, I'm confident it's a network issue and not an AutoCAD or Office issue only. I tried to open a file across the network using Notepad, and it locked that up also. Ridiculous I say.

Off to the net for more google! Any more suggestions are greatly appreciated. I'll try not to be too much of a pain in the ass today.

Edit: The Server is Windows 2003 Server R2 with Service Pack 2.

Papa_Complex · 12-05-2008, 09:43 AM

OK, so the fact that it's at SP2 confirms that the known folder access speed issues that I was able to find have been dealt with. I've got a coupl eof work orders to take care of first thing this morning but Fridays are usually slow around here, and it's exam time, so I'll have some more time later to dig into it for you.

12-05-2008, 08:21 AM	#1
G-Rex Where to next? Join Date: Nov 2008 Location: OK to the C Moto: TL1000R, Hayabusa, R1150RT Posts: 1,333	Computer peeps..Server 2003 question.. Ok, so I just connected a new Windows 2003 Server, accessing it with Windows XP Pro and Windows 2000 Pro. I don't have the whole thing online totally yet, as the old NT server is still running, because of a problem I am having. The main job of the server is file storage. I do have it set up as a PDC, with DNS and DHCP configured. The problem I am having is file access. When I try to open an AutoCAD file, the system practically locks up. It drags to the point that it tells me the file is invalid. I can copy the same file to my hard drive and it opens quickly and perfect. No troubles. The cabling is not in question. Connectivity is fine. Even Word and Excel drag a little bit, but at least they open. Although, if i open Explorer and try to double click on the file there, it will lock the system up too. I'm at my wits end and any suggestions would be very welcomed! I'm going to call Dell this morning and hope that I talk to someone I can understand. I haven't had such good luck with that in the past. __________________

12-05-2008, 08:29 AM	#2
Papa_Complex Nomadic Tribesman Join Date: Nov 2008 Location: Brampton, Canada Moto: '09 ER-6n Posts: 11,150	It might help the server types if you can say how you're accessing it. Are you using UNC pathnames? Drive mappings? Are there any UNC pathnames or drive mappings that have recently been eliminated? This can result in long delays, while Windows decides whether the dead links are still valid. If you have the "Web Client" service enabled on the XP box (it is by default), then XP will look for web content on any folder that it tries to open. This also slows things down. Then there's the way that Windows looks for Scheduled tasks on every remote folder. I don't have the registry hack handy, but it's one entry that needs to be changed, in order to disable this. EDIT I did a quick search and found that system time settings can also cause issues with remote access speed. Have you matched the time zone on the 2003 server to your location and are both systems time synchronized (or at least close)? Last edited by Papa_Complex; 12-05-2008 at 08:34 AM..

12-05-2008, 09:10 AM	#4
Papa_Complex Nomadic Tribesman Join Date: Nov 2008 Location: Brampton, Canada Moto: '09 ER-6n Posts: 11,150	It's worth manually checking the date, time, and time zone settings on both boxes, just to be safe. As I've frequently found over the last 20 years of desktop support, just because something SHOULD happen, that doesn't mean that it DOES You would be best off removing the NT box from the network while testing this, so obviously this will have to be done at a time when production isn't necessary. It's easy to disable Web Client on the XP box. If that doesn't help, then you can always re-enable it later. Go into Control Panel and set it to "classic view", then call up Administrative Tools, then services. Scroll down toward the bottom and find Web Client. Double click it, stop the service, then set it to disabled. Reboot and try again. Clear the "recent documents" list from the XP box. Make sure that there are no links in My Network Places that point to resources that no longer exist. Turn off the antivirus, or uninstall it completely. See if you can access the shares faster via IP address than by name (I've seen this more than a few times). I looked around and found the registry entry for Scheduled Task searches on remote computers. It's in this location in the registry, on the XP box: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\Curr entVersion\Explorer\RemoteComputer\NameSpace\{D627 7990-4C6A-11CF-8D87-00AA0060F5BF} First export it so that you can restore it later, if you want to. After that, delete that registry entry and reboot. There's another entry in the same group for printer searches that can be deleted too, with the same recommendation to back it up first. This used to be a HUGE speed issue here, when we had a mixed Windows/Novell server environment. Another EDIT I forgot to ask what service pack level the server was at. Last edited by Papa_Complex; 12-05-2008 at 09:30 AM..

12-05-2008, 09:39 AM	#5
G-Rex Where to next? Join Date: Nov 2008 Location: OK to the C Moto: TL1000R, Hayabusa, R1150RT Posts: 1,333	Ok Rob, I verified the time stamp is the same on both system. I also disabled Web Services on my XP system, and deleted the two registry keys you suggested. I am still having the problem. Although now, I'm confident it's a network issue and not an AutoCAD or Office issue only. I tried to open a file across the network using Notepad, and it locked that up also. Ridiculous I say. Off to the net for more google! Any more suggestions are greatly appreciated. I'll try not to be too much of a pain in the ass today. Edit: The Server is Windows 2003 Server R2 with Service Pack 2. __________________

Thread Tools
Show Printable Version Email this Page
Display Modes
Switch to Linear Mode Hybrid Mode Switch to Threaded Mode

12-05-2008, 09:43 AM	#6
Papa_Complex Nomadic Tribesman Join Date: Nov 2008 Location: Brampton, Canada Moto: '09 ER-6n Posts: 11,150	OK, so the fact that it's at SP2 confirms that the known folder access speed issues that I was able to find have been dealt with. I've got a coupl eof work orders to take care of first thing this morning but Fridays are usually slow around here, and it's exam time, so I'll have some more time later to dig into it for you.