Rickhdee
asked on
Win7 Reports it cannot connect to server - but does
Server: WS2008-R1 32-bit. PC's: Win7-64. Network 1G - 2 Switch Hop.
Description: When new win7 pc's boot up they complain that they could not connect to the mapped network drives and the drive icons in My Computer show a big red X. Clicking on any of them and the share comes up immediately. Log files show the PC is not finding a DC to service it. This includes not setting the time, not processing group policy settings, etc. However, it does connect and it does eventually do all these things. About a minute and a half from boot before all the errors in the log file having to do with letting the pc attach to the domain are resolved.
My thinking is that the new win7 boxes, with SSD drives, I7 processors, etc are just so fast that they request various things from the server and because of a slight lag they error and complain. Make any sense? If so, would there be a way to retard there over-reaction to the delayed response from the server? Or is this a network connectivity problem? Replacing older PC using same cabling to the net results in these erorrs whereas the older, slower boxes never complained.
Again, you can access any of the mapped drives instantly, after the system complains they cannot be connected and replaces the drive icons with red x's.
Thank You.
Description: When new win7 pc's boot up they complain that they could not connect to the mapped network drives and the drive icons in My Computer show a big red X. Clicking on any of them and the share comes up immediately. Log files show the PC is not finding a DC to service it. This includes not setting the time, not processing group policy settings, etc. However, it does connect and it does eventually do all these things. About a minute and a half from boot before all the errors in the log file having to do with letting the pc attach to the domain are resolved.
My thinking is that the new win7 boxes, with SSD drives, I7 processors, etc are just so fast that they request various things from the server and because of a slight lag they error and complain. Make any sense? If so, would there be a way to retard there over-reaction to the delayed response from the server? Or is this a network connectivity problem? Replacing older PC using same cabling to the net results in these erorrs whereas the older, slower boxes never complained.
Again, you can access any of the mapped drives instantly, after the system complains they cannot be connected and replaces the drive icons with red x's.
Thank You.
ASKER
mfulksCBT,
Interesting reading and a lot to absorb. I will examine all group policy settings to see if there is anything that can be removed and to get a better feel for what is going on. This will probably take some time to digest.
Interesting reading and a lot to absorb. I will examine all group policy settings to see if there is anything that can be removed and to get a better feel for what is going on. This will probably take some time to digest.
This usually happens when Fast Logon Optimistion is enabled - which is it by default.
The instructions to disable are in the link that mfulksCBT gave you.
Enable - Always wait for the network at computer startup and logon in GP.
The instructions to disable are in the link that mfulksCBT gave you.
Enable - Always wait for the network at computer startup and logon in GP.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Bitsbytesandmore,
You have certainly done your research. I will start with DIIRE's fast login op. and go from their. Much to try.
You have certainly done your research. I will start with DIIRE's fast login op. and go from their. Much to try.
ASKER
Trying to determine if it is actually a wiring problem I placed a switch with just a 2 ft cable next to two boxes reporting the error. This eliminates the error "can't connect all network drives" at boot time. Very strange. If the connection from the point of the new switch to the next switch down the line was bad, you would think you would still get the error. But perhaps the switch acts to boost power on the connection? Am continuing to test.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
BitsBytesandMore, you have done a great job detailing all the things to try, I just haven't had the time yet as these machines are also in use everyday. I make changes and ask the users to report on their boot time experience. I have a new win7 box on the bench though so will be reviewing and trying all the options this week and should have a resolution using one of the methods listed or will just have to indicate no solution yet.
No problem. I'm not going anywhere...Lol. I will keep monitoring this thread for your results.
Bits ...
Bits ...
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
I believe (just in my humble opinion) that post ID: 35055670 and post ID: 35189547 together with the OP's own analysis "...are just so fast that they request various things from the server and because of a slight lag they error and complain..." and his own testing in ID: 35189040, cover most of the known causes of the error: "...could not connect to the mapped network drives...". It would be a pity to delete this question and not allow it to remain and be available for future reference.
I understand that because this is not a crippling error, because it is intermittent and because of other daily pressing demands on other issues in an IT department, this problem gets relegated to the back-burner, nevertheless, it can be very annoying and unsettling and gives the network user the feeling of an unstable environment (even if in reality it is not).
Bits ...
I understand that because this is not a crippling error, because it is intermittent and because of other daily pressing demands on other issues in an IT department, this problem gets relegated to the back-burner, nevertheless, it can be very annoying and unsettling and gives the network user the feeling of an unstable environment (even if in reality it is not).
Bits ...
A much to valuable question, with so much time invested to allow it to die. The mapping issue which has created so many threads in so many forums is very common and annoying . My recommendations are as previously stated above.
Bits ...
Bits ...
http://technet.microsoft.com/en-us/library/cc758898%28WS.10%29.aspx