Jump to content

Recommended Posts

Posted

My SIMS server is a P2V server 32bit2003r2 box. so I'm running on VMware ESX 4.0. The server won't let me RDP in and the console login has been tryin over the weekend. The server is still doing all it's sims stuff fine. I sheduled a reboot last night but it didn't do it. Also Vmware also can't back it up or snapshot it.

 

ideas?

Posted
(using MMS) the error log only shows authentication errors for users accessing the S Drive using the wrong domain? (servername\username instead of domain\username. But I've had no reports of users not being able to access the s drive or use sims.
Posted

Also in my experience, it sounds as though there may be a problem with explorer.exe or that the explorer.exe process is not running.

 

I've only ever seen this sort of behaviour on 2003 and not 2008 R2.

Posted
Also in my experience, it sounds as though there may be a problem with explorer.exe or that the explorer.exe process is not running.

 

I've only ever seen this sort of behaviour on 2003 and not 2008 R2.

@Michael it is a server 2003 server.

Posted

can you send a reboot command via shutdown/restart command ?

 

Shutdown.exe -i , and add the server name to it .. and set the options for the reboot

Posted

First of all I would check that VMware Tools is installed and up to date. I would also remove any software which would be previously interacted with hardware such as some of the HP system manager software etc. These can cause severe performance issues.

 

Do you get any errors with the VMware snapshots that you can post up?

Posted

What has been changed (if anything) on the server between RDP working and it now not working?

 

Specifically, there was an April patch that could break RDP for 2003 servers until you removed an old patch, installed the April patch and the reinstalled the existing patch.

 

Think it's this one: MS12-024: Vulnerability in Windows could allow remote code execution: April 10, 2012

 

And hotfix: RDP clients and ICA clients cannot connect to a Windows Server 2003-based terminal server after hotfix 938759 is applied to the server

Posted
I know that update, i installed it early a few weeks ago, it did'nt break the system. Plus I was logging into the console through vsphere. I do have APC powerchute but it's pretty uptodate. What i am puzzled about is the fact i haven't configured anything recently? the last bit of software i've installed is the vivo extractor thing. I've now disabled all shueduled tasks and the server is still ok. the tasks were, groupcall, vivo, and discover. the server hasa 2gb and is using 1.7 of it. but a memory shortage should have popped up in vsphere.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now



×
×
  • Create New...