• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 977
  • Last Modified:

New Windows 7 Box slow on server 2003

I just put a brand new Windows 7 SP1 Box on existing network.  When I map a drive on the server, the Drive opens VERY slowly and I cannot open a sub folder on mapped drive at all.  All other computers on Network are XP and all work fine.  So far no solution I have found will work.
0
annonamos
Asked:
annonamos
  • 7
  • 6
  • 5
3 Solutions
 
exponeCommented:
(1) Is your Server 2003 up to date with all Windows updates? You should run all updates on the server, otherwise Server 2003 wouldn't even know about Windows 7 operating system.

(2) Have you joined your Windows 7 PC to the server's domain? If not, have you created username and password on the server so that it is matching username and password which you are using on Windows 7 PC?

If you don't have any password on Win7 PC, create a password and make sure that the same username and password is defined on the server.

0
 
annonamosAuthor Commented:
Yes the Windows 7 machine is joined to the server.  Log on is normal and drive mapping happens automatically.  I can see the entire network in explorer.  Server and new windows 7 PC have all updates installed.  
0
 
exponeCommented:
Then you may try slowing down your LAN card in Win7 PC, as it is probably set to "Auto", so you may wish to try 100Mbps Full Duplex, as per attached screenshot (please let me know if you can't find it, so I'll post some notes on how to get there :-)  LAN Card Settings LAN Card Settings
0
Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

 
annonamosAuthor Commented:
Do not have "media type" but I believe "speed & duplex" is the same thing.  Tried changing settings but no change.
0
 
exponeCommented:
Yes,  "speed & duplex" is the same thing. Are you able to login as "Domain Administrator" on the PC and check the speed?
0
 
bluemercuryCommented:
It's a wild shot in the dark, but I had a distantly related problem recently. I discovered that, from Vista onwards, Microsoft have introduced SMB version 2. On the server side, Win 2003 will be using SMB version 1 (it is all it knows), and your Win 7 Client should merrily switch back to using this.

I just wonder if it is hanging for a short while though, trying to use SMB 2 with the server, when it can't. Then it finally timeouts, and reverts to a legacy mode (or just goes a bit AWOL).

Like I say, shot in the dark, but here is the article that I found on the web when I had a somewhat related problem: http://www.petri.co.il/how-to-disable-smb-2-on-windows-vista-or-server-2008.htm

Bear in mind you'll be doing this on the client side, and if you have any other 2008 servers, they won't be able to benefit from a SMB 2 connection.

Good luck!
0
 
exponeCommented:
In Win 7, go to the Control Panel, and go to Network & Sharing Center.  Go to Change Advanced Sharing Settings link on the left and under Home/Work settings, change the File sharing connections from Use 128bit encryption, to Enable file sharing for devices that use 40-56bit encryption........this seemed to fix a similar issues we had on our domain with the Win 7 system.
0
 
annonamosAuthor Commented:
I can log in as Domain Administrator but I am not sure as to what speed you are referring to or where to look.

I tried disabling SMB 2 on Client but no help.

I changed file sharing from 128 to 40-56 encryption but no help.

Although it is very slow, I can get into the root of the mapped folder after a 20 second or so delay.   I have not been able to access any sub folder at all.  It just tries to continue loading.  No error messages.  After trying both suggestions,  A sub folder opened after about 5 minutes, maybe longer.  ( all XP machines on the system open these files instantly) .  
0
 
bluemercuryCommented:
I know it would be a very strange annomally, but have you tried resetting all systems, and any switches you are operating on the network? I had a similar issue once, and it was because a switch had gone rogue, temporarily generating a massive amount of garbage bandwidth. Bizzarrely, it only effected one or two systems connected to specific ports on a managed switch, and the rest were fine. On reset of the switch, the problem went completely away.

Just a thought - sorry if that is of no help. Good luck :)
0
 
annonamosAuthor Commented:
I cannot explain it but I just rebooted the server again and the situation resolved itself.  Everything is running normally.  I think I will leave SMB 2 disabled and the encryption level where it is.  I have turned the LAN card back to auto. Thank you all for helping. I would be happy to give credit but I have no explanation for it suddenly working.
0
 
bluemercuryCommented:
Did you reboot before when you altered the registry settings, etc, to disable SMB 2? The alterations would have not taken hold till a reboot - would be interested to know if you did do this before, and if you didn't I would say it is probable that this did the trick.

Otherwise, it shows that even in this day and age, so many problems still get randomly fixed by a few reboots; the joys of computing! :)
0
 
exponeCommented:
It is relatively easy tu turn back on 128 bit encryption and test, but if you don't want to lose any more time on this, just split the points, as we all tried our best to help :-) Bluemercury, do you agree?
0
 
bluemercuryCommented:
expone - I would say that is fair call. I think either the encryption switch you suggested or the SMB 2 will have fixed this problem (or who knows, maybe a combination of both!), and I'm sure that this resolution will be helpful to someone else trying to Google this problem.

Happy to share the points :D
0
 
annonamosAuthor Commented:
Well in the interest of following through to the end, I reset the encryption to 128 bit .  I rebooted and tried system.  There was no apparent change.

 Next, I changed back to SMB2 and rebooted.  Although it was slight, I believe their was a discernible  difference.  This of course is anecdotal as I was not using any true measurement,  just observation. I switched back to SMB 1 and left it there as it seems to function better.  Thanks for the help.  
0
 
annonamosAuthor Commented:
While there is not a clear cut answer to which of these solutions may have fixed this problem, if either, the proposed solutions were both uniquely viable. All I can attest to is that while following both of these suggestions, the problem was solved.
0
 
bluemercuryCommented:
Hi annanamos.

Thanks for your comment and points. These weird anomolies happen. Let's hope that should the problem ever happen again (I hope they don't for you!) either of the solutions might present a solution.

Best of luck with your projects :)

Bluemercury
0
 
exponeCommented:
Yes, this post contains many "golden nuggets" from our diverse IT networking experience and therefore I would be very sad to see it deleted from Experts-Exchange database, as it may provide a quick help to many other IT consultants who are often under pressure from their boss (or customer) to get a quick fix for their slow network.
0
 
annonamosAuthor Commented:
Thank you for the help.
0

Featured Post

Free Tool: ZipGrep

ZipGrep is a utility that can list and search zip (.war, .ear, .jar, etc) archives for text patterns, without the need to extract the archive's contents.

One of a set of tools we're offering as a way to say thank you for being a part of the community.

  • 7
  • 6
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now