Problem with restart/shutdown on windows 2003 R2

[pbornacin]

Hi to everybody, I have installed UltraVNC 1.0.8.2 on a few servers with windows 2000 and windows 2003 R2:
when I try to restart or when I try to shutdown servers with windows 2003 R2, instead of closing the server, the user is disconnected .
With windows 2000 everything works correctly. Do you have any idea about the reason of this problem?

Do you know if anybody else has already faced such problems?
I carried out several researches but I have not found anything.

thanks and best regards

p

[B]

When you say "shutdown servers" do you mean shut down the VNC server, or shut down the Windows server entirely?

What, exactly, happens "correctly" when you do it in Windows 2000?

[pbornacin]

>When you say "shutdown servers" do you mean shut down the VNC server, or shut down the Windows server entirely?
I mean shutdown the Windows server entirely.

>What, exactly, happens "correctly" when you do it in Windows 2000?
When I try to reboot the windows 2000 server, the server is rebooted, not only the user is disconnected

P

excuse for my poor english... sorry

[B]

Okay, I understand.

That's weird though. Are you sure that you're specifying a shutdown and not a logoff (or restart)?

The only other thing I can think of is that you may need to run the VNC server as a service to retain control at that point. Possibly a UAC issue?

[pbornacin]

>[...]
>That's weird though. Are you sure that you're specifying a shutdown and not a logoff (or restart)?
Yes, i'm sure, i try on various server and with the support of my colleagues (

>The only other thing I can think of is that you may need to run the VNC >server as a service to retain control at that point. Possibly a UAC issue?
I try with various users (also with the domain administrator)...

[B]

Okay, but is WinVNC running as a Windows <b>service</b>?

[pbornacin]

>Okay, but is WinVNC running as a Windows service?
yes, but we have found the problem: if i set "Logoff workstation" When the last client Disconnects on UltraVnc settings, the server allways logoff the user but never shutdown/reboot (on Windows 2000 too).

bye

P

[B]

No kidding? That almost sounds like a UVNC bug then. If you were able to successfully initiate a shutdown via the Windows GUI, the system should still shut down, regardless of UVNC settings.

[pbornacin]

>No kidding?
no kidding, i tried on 2 windows 2003 R2 server with the same result.

>That almost sounds like a UVNC bug then. If you were able to successfully >initiate a shutdown via the Windows GUI, the system should still shut down, >regardless of UVNC settings.
I'agree with you, if you can test yourself...

bye

P

[B]

Well, whaddya know! I was able to duplicate the problem to an XP station too!

I had to change my setting in ultravnc.ini as per [topic=18007][/topic]

Sure enough, when I told the system to shut down, it logged off instead, and left the station at a Ctrl-Alt-Del prompt (I'm on a domain).

Even more interestingly, if I tried the shutdown from the <b>physical station</b> while the VNC session was active, it STILL didn't really shutdown, and instead returned to the login prompt again as above.

Only when no VNC session was in effect could I shut down the station.

I'd say that's a pretty serious bug!

P.S. I encountered the usual UltraVNC weirdness too; after a first failed shutdown/logoff, when reconnecting to the service and logging in again via UVNC ("chunkviewer") the screen display was not being updated at all, except upon manual refreshes.

[redge]

work around for force shutdown service uvnc_service

start "cmd.exe" as administrator
sc stop uvnc_service
close cmd

the long time known bug never been solved about
"When last client disconnect"
ultravnc.ini
LockSetting=1 =="Lock Workstation (w2k)"

parser mice/keyboard are buggy only in this area was known by UltraSam

[YY]

work around for force shutdown service uvnc_service

start "cmd.exe" as administrator
sc stop uvnc_service
close cmd

This method is OK, but not applicable to pbornacin's situation ..... once uvnc_service stopped, he can't proceed to restart that pc REMOTELY.

Another workaround is using a shutdown/reboot tool with delay feature, like the Windows' buildin tools shutdown.exe or tsshutdn.exe. When got connected, you may run such command at the server pc, log out then and the server should reboot after the specified time.

See this site for a reference.

[B]

Couldn't you also just take redge's script and add a "shutdown" command to it? That would probably work too...