Windows 7 Thread, Random Windows 7 problem! (Logon) in Technical; I'm scratching my head over this one
Users have roaming user profiles, located in \fps1\staff_profiles$\username
They also have a home ...
19th August 2011, 01:23 PM #1
Random Windows 7 problem! (Logon)
I'm scratching my head over this one
Users have roaming user profiles, located in \\fps1\staff_profiles$\username
They also have a home area, \\fps1\staff$\username
On random machines and at random points a user will attempt to log on and receive a blank desktop with an error message:
Their Desktop folder is redirected to a Desktop folder in their home area.
The bizarre thing is, they also seem to then have no access to their H:\ drive which is specified in the login script to map to their home area directory, however they can access G:\ and I:\ drives which are shared directorys on the same fps1 server?!
As soon as they log out and log back in to the same machine things seem back to normal.
Like I mentioned, totally random!
IDG Tech News
19th August 2011, 01:29 PM #2
Sounds daft but are the machines they go to randomly dropping the network connection ? if they log off and back on again do they get the correct settings ? All I'm thinking is maybe the switch has STP or there is some kind of timeout on the NIC, which means if you login you may not pull down profiles correctly. The new HP machines we have have got whats called Green Ethernet and it means when the computer goes to sleep once you wake it back up it takes A minute or so for the power to the NIC to be resumed which also explained why our wake-on-lan didn't work.
19th August 2011, 01:33 PM #3
If you right click the desktop and choose 'refresh' or open up Task Manager and Stop/Start Explorer, what results do you get?
19th August 2011, 01:35 PM #4
19th August 2011, 02:22 PM #5
Spanning Tree Protocol...We do have that turned on and have noticed it is being funny with the DHCP but didn't know if we could turn it off without buggering anything else up?!
19th August 2011, 03:10 PM #6
If Spanning Tree isn't setup properly, you will get loopbacks and this is why you would in theory have problems with DHCP. As a result, this would appear why you're losing connectivity with your server(s).
19th August 2011, 04:40 PM #7
Some thanks to me then for bringing up that old STP lol you should be ok enabling port fast on your switches.
19th August 2011, 05:02 PM #8
Thanks - Will look into portfast
19th August 2011, 06:29 PM #9
What switches do you have ?
20th August 2011, 08:35 PM #10
Can I ask some questions?
This message to me means the computer cannot contact the server now this can happen for many reasons like the machine has not received a dhcp address so cannot find the network, the dns is not working correctly so cannot find the server.
Are your ip addresses set by dhcp?
If they are does this only happen when a machine is newly turned on? Sometimes a computer can start too fast for the network and people can log on before the ip address is received so people can log on and do not receive a profile as the computer cannot contact the network. This can be helped by changing a group policy to wait for network and a registry setting to wait for wait time while policy settings are received. I am sorry I cannot remember this setting off the top of my head as I am not at work. A lot of the time this can happen if a lot of network traffic is on the network. Use a traffic sniffer to capture some traffic on the server and analyis it to see if you have corrupt packets or a broken nic or lots of 2012 errors on windows 2008 and windows 2007 r2 servers. Have a look for a lot of arp requests for machines that do not respond like gpos that have old paths that do not exist.
Does this happen if a machine has been on for a while and not been used? We had a problem where eco settings on the nic cards turned them off under powersavings. We also had this problem is say a 1 gig network card in a client was plugged into a 10/100 switch and the nic had problems negotiating a connection speed.
Have you turned tree spanning on you switches this can stop loops which can cause a lot of traffic and arp requests.
Have a see if all the computers connect to the same switch and see if they have the same problem if you move them to another area of the school to see if you have a bottle neck on the network. We had to upgrade a main feed to a switch cabinet to fibre when we updated machines as they needed traffic quicker then the network could supply.
These are only ideas.
20th August 2011, 08:40 PM #11
The gpo for Always wait for the network at computer startup and logon to the computer can be found here: Computer Configuration\Administrative Templates\System\Logon
Have a look at Windows 7 Clients intermittently fail to apply group policy at startup for reg setting for waiting for policies.
20th August 2011, 08:43 PM #12
I am sorry I forgot check to see if you are running out of dhcp addresses and check dns works.
20th August 2011, 08:45 PM #13
Have a look at Colasoft - Free Network Analyzer for Windows & Retrospective Network Analysis Software for a free analyser for network traffic if will help you identify if you have a network traffic problem.
22nd August 2011, 08:45 PM #14
- Rep Power
Not related to your error, but its always a bad idea to map drives to a $ share as they are ment for admin use only. This could have an issues on the error your getting.
By DrCheese in forum Windows 7
Last Post: 17th August 2010, 12:07 PM
By eddyc in forum Windows 7
Last Post: 26th March 2010, 09:34 AM
By Steven in forum Windows
Last Post: 26th October 2009, 10:57 PM
By LeightonJames in forum Windows 7
Last Post: 23rd October 2009, 09:36 PM
By mossj in forum Hardware
Last Post: 1st May 2009, 11:53 AM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)