Windows Server 2008 R2 Thread, Logon stuck at "Please wait for the user profile service" in Technical; Why it is what should be a simple thing turns out into a headache of mammoth proportions?
Server 2008r2 DC.
7th August 2013, 12:41 PM #1
Logon stuck at "Please wait for the user profile service"
Why it is what should be a simple thing turns out into a headache of mammoth proportions?
Server 2008r2 DC.
Due to a subnet change I need to change the address of the server. Should be a simple thing right? I thought so. I make the address change and setup a new DHCP scope but none of the clients can connect so from the server I ping the server but I get back an IPv6 address so I’m guessing this if why the clients can’t connect. I flush DNS, clear the DNS cache, restart the server but still no IPv4 address so I disable IPv6 on the NIC and restart. I go to login and now I’m getting “Please wait for the user profile service”. I give it 5 minutes and crash out and try booting into safe mode so I can enable IPv6 again but it won't accept the password. I restart the server normally and try to log in and get the “Please wait for the user profile service” which it has been stuck on for 40 minutes now.
IDG Tech News
7th August 2013, 01:02 PM #2
Did you update the dns A record for the server?
7th August 2013, 01:06 PM #3
I checked and it was listed correctly
7th August 2013, 01:08 PM #4
Well step one is install this:
An enterprise hotfix rollup is available for Windows 7 SP1 and Windows Server 2008 R2 SP1
Not that it will help in this case... but it will probably solve lots of little problems you might not have realised you were having.
Back to the problem at hand:
Are all your servers have the correct IPv4 settings i.e. are all there addresses, subnet masks, and default gateways correct?
run ipconfig /registerdns on all your servers.
Are your servers able to ping the default gateway?
Are your servers able to ping each other (by IP, then FQDN)?
Cab they ping any of the clients (by IP then FQDN)?
Are your clients able to ping the default gateway.
Are your clients in the same VLAN as the servers (by IP then FQDN)?
What happens if you manually configure the IP settings for a client to be correct, and then repeat the tests above?
Last edited by psydii; 7th August 2013 at 01:09 PM.
7th August 2013, 01:10 PM #5
If you have VLANs, then perhaps you need to change the UDP helper / DHCP relay config in your router to point to the new IP of your DHCP server?
7th August 2013, 01:11 PM #6
There is only one DC and I can't logon to it to make any changes. Before the restart I could ping the gateway and the internet worked ok.
7th August 2013, 01:11 PM #7
Originally Posted by psydii
7th August 2013, 01:13 PM #8
It's now been 65 minutes and I'm starting to bite my nails!
7th August 2013, 01:23 PM #9
Been a while since I broke a DC... but I wonder if the problem is the DNS server entries in the IP Settings?
You might be able to use the "http://blogs.technet.com/b/meacoex/archive/2011/08/15/reset-your-windows-sever-2008-r2-domain-controller-administrator-password.aspx" trick to get a command prompt and check and, if necessary change your IP Settings with "netsh"
7th August 2013, 01:30 PM #10
I didn't change the DNS settings on the NIC!
Originally Posted by psydii
Hold on yes I 'm sure I did. I'm starting the server using the last known good config now so fingers crossed!
Last edited by Jobos; 7th August 2013 at 01:37 PM.
7th August 2013, 01:37 PM #11
Use the break in trick and set the interface DNS settings.
netsh int ipv4 dump >c:\intIPv3Dump.bkp (backs up the current config)
netsh int ipv4 set dnsservers name="Local Area Connection" static 127.0.0.1 primary (self explanatory I hope.)
7th August 2013, 01:41 PM #12
Servers come back up and the NIC settings are correct so it must be because I disabled IPv6?
7th August 2013, 01:46 PM #13
Glad to hear it!
If you are not using VLANs then Windows 2008 R2 and Windows 7 default to ipv6 for communication... they also try if you are using vlans, but your switch config can get in the way, which is why many people completely disable ipv6 for Vista and above. Also: Arguments against disabling IPv6 - Romania Networking Team Blog - Site Home - TechNet Blogs
Are both your ipv4 and ipv6 registered in your DNS?
7th August 2013, 02:03 PM #14
I think I'm almost there. Clients can connect to the server now and I can ping the server from my pc and get the correct IPv4 address but pinging the server from the server still gives the IPv6 address unless I use the ping -4 servername which then I get the IPv4 address.
DNS still has the old reverse lookup zone listed and not the new zone.
7th August 2013, 04:33 PM #15
Now that's coincidental, is there an update that may have cased this as we just had the very same thing happen, waited about an hour before I could get in then it all looked OK...but...I then logged off and was then stuck at the the loading group policy objects! No way but wait for my friendly more knowledgeable engineer to dig me out of it. He eventually got back in (Active Director Restore Mode) after a hard reset and it was something to do with the DNS it seemed, looked to have forgotten its settings, thought it was a one off till I saw your message. Try logging off and see what happens.
By adhutton in forum Windows 7
Last Post: 22nd May 2013, 12:10 PM
By FN-GM in forum Windows Server 2008 R2
Last Post: 30th April 2012, 04:03 PM
By witch in forum Windows Server 2000/2003
Last Post: 24th February 2012, 09:26 AM
By doombadger in forum Windows 7
Last Post: 13th October 2011, 11:40 PM
By eddyc in forum Windows 7
Last Post: 3rd February 2011, 02:46 PM
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)