Server 2003 renamed to 'Whistler'

[markman]

I have a server 2003 file server that has changed its OS name to 'Whistler'. I can still log into it at the server but I can't log in remotely. I have Googled it but there doesn't seem to be anything out there. The OS was installed from a 2003 disk.

 

Ideas anyone??

 

Thanks in advance

 

Mark

[Gatt]

That's its codename isn't it?

Where is it being referred to Whistler? IIRC you could reghack some of the files to retrieve the images

[markman]

Yes, whistler was the codename, its at the log in screen. and refusing remote access, as soon as you put a password in it kicks you out?? Strange.

[FN-GM]

Yes, whistler was the codename, its at the log in screen. and refusing remote access, as soon as you put a password in it kicks you out?? Strange.

 

I had this when upgrading to a service pack. From what i could gather the whistler stuff is still hidden in the OS. Everything worked fine to be honest didnt have the problems you did.

[glennda]

Try replacing the MSGINA.dll - its the part which supplies all the images to the login box etc.

[sukh]

Hi

 

Do you get any error messages when you try to RDP?

Can you login locally and check the event logs for errors?

Can you telnet to 3389 on the target server from a PC?

Can you RDP using the /admin switch?

 

Sukh

Edited April 7, 2011 by sukh

[markman]

Thanks, I'll run through the suggestions.

[dan_pricE_101]

Did anyone find a fix for this in the end? I am having the exact same issue where its reverted back to whistler and cannot logon remotely. bit of a kick in the ...... considering the server is mounted in the most awkward cabinet

[sted]

Did anyone find a fix for this in the end? I am having the exact same issue where its reverted back to whistler and cannot logon remotely. bit of a kick in the ...... considering the server is mounted in the most awkward cabinet

 

could you remotely install vnc on it and then use that to get to the console session?

[gshaw]

When you login to the server right click My Computer and check the OEM support info on System Properties. I've got a hazy memory of a bit of malware that changed the computer name and OEMInfo a few years ago, might not be the case for you but worth double checking...