Win2k3 logon issue Please halp!!! 3

[favit]

I just recently installed win2k3 server on my machine. I gave it an IP and shut it down. I realized there was an ip confict with another machine when I turned it back on and so I changed the IP. Since I've done that. Everytime I turn on the winw2k3 server and logon it does not go anyware. It just stays on the blue screen after I have loged on. I have pressed cltr, alt, delete and shut it down. I tried ending explorer and starting it again but to no avail. What should I do next?

Most appreciative,

 

[porkchopexpress]

Try starting in safe mode.

Remove all floppy disks and CDs from your computer, and then restart your computer.

Press F8 after the firmware POST process completes, but before Windows displays graphical output.

From the Windows Advanced Options Menu, select a safe mode option listed in the following list.

 

[adcfaq]

boot into safe mode
uninstall NIC drivers
boot again
install NIC by orginal CD or Disk

 

[favit]

I just did what you guys said and still when I logon it still stay there doing nothing just bluecreen so I just hit ctrl, alt delete and shutdown and restart.

 

[porkchopexpress]

It might be worth logging it on and leaving it fot 15 minutes i've known Windows suddenly spring to life after this amount of time, if this server is not your DNS server and the NIC now has the wrong DNS IP address it might be pausing and looking for a DC. Thats just a complete shot in the dark as i don't know your setup.

 

[favit]

Eventually, after I logon and I see the blue-screen I wait for at least 20min. Then it logs in and I can see the desktop. Any reason why? or is there a cure for this issue.

 

[porkchopexpress]

Well how is the server setup, DNS misconfig can cause this with Win2k3 servers.

 

[favit]

I have not configured the dns yet. Its just a stand alone right now.

 

[favit]

I have not configured the dns or wins nor converted it to a domain controller. Its just a standalone.

 

[porkchopexpress]

If it is still taking a long time to login i'd try benlu's suggestion and reinstall the NIC drivers, altering that is what started the problem so it's a good place to start.

 

[favit]

I have uninstalled and re-installed the nic card and it is still doing the same. What next?

 

[porkchopexpress]

Are there any errors in the event log?

 

[favit]

I will let you know in 20min as soon as it starts up again.

O.K

 

[favit]

The only error with a red x on it, that I see in the event viewer is as fallows:

Description:
The device \Device\IdlePort1, did not respond within the timeout period.

Source: atapi
Even ID: 9

 

[SMBgeek]

favit, check out this link and see if it helps. You may have a bad Hard Disk or CD drive that is throwing errors.

http://www.eventid.net/display.asp?eventid=9&eventno=2060&source=atapi&phase=1

Regards.

SMBgeek

http://www.smbgeek.com

 

[porkchopexpress]

That is a possibility it might be worth running a disk check utility.

 

[favit]

Thanks,

I have fixed it already by changing the Cd rom, but thanks for the link.

Most Appreciative,

 

[porkchopexpress]

Of course Source: atapi is a bit of a give away should of seen that

Glad you sorted it.

 

[favit]

Appreciate all the help.