Windows 2003 asks for the password but refuses the connect

[Dennis]

And yes for all of you saying im using the wrong password, I'm not. I have tried with other vnc servers and they do the same thing. The firewall is disabled(not that it would ask for a password if it wasnt) but as soon as i put in the password it just says "Authentication Failure". I'm guessing it has something to do with windows 2003 cause it works fine on my xp box at home. Any help would be greatly appreciated. Thank You!

[redge]

VNC authentication or MS Logon authentication ?
if MS Logon, you need to complete field VNC password even is not used.

[topic=58][/topic]
[topic=3309][/topic]

open Windows Task Manager (Ctrl+Alt+Del) on vnc server)
look tab Processes
Image Name | User Name | CPU |Mem Usage
winvnc.exe | SYSTEM | 00 | 3'xxx K <<-- system mode
or
winvnc.exe | redge | 00 | 3'xxx K <<-- user mode

WinVNC: Default Local System Properties = SYSTEM


WinVNC: Current User Properties = redge

[Dennis]

It's after I put in the password the vnc server asks me for. It just disconnects me, doesn't say wrong password or anything. Just a simple "you have been disconnected, would you like to reconnect?" I've set the password over and over again but it still wont work. Even if I remove the password it will just disconnect me. It's like windows 2003 refuses the password/connection not the vnc server or something but theres no firewall. I honestly have no idea why it wont work and have spent hours searching forums and google and noone has a direct answer. Most replies are just guesses relating to a user overlooking something or a firewall.

[samdu]

I'm having the exact same problem. Dennis, do you have a router between the 2k3 box and the Internet, or are you running SBS with the built-in router active?

[samdu]

Alrighty! I resolved this problem on the server I was dealing with. I was running F-Secure AntiVirus For Servers on the machine. I uninstalled it, and VNC came right up. Not sure why an antivirus would be interfering with anything non-virus related, but there ya go.

Back up, F-Secure wasn't the problem. BUT - I DID find the problem. Well, actually, the ISP found it. It was a problem with the settings on the Gigabit Ethernet connection (Intel GB on the motherboard of a Dell Server). There's a setting called Offload Recieve IP Checksum that is supposed to do error correction. Apparently it works really well unless the connection isn't full. If the connection isn't completely utilized to near capacity, however, it causes a bottleneck as it sends packets back to the NIC for inspection. Turning that off (default is on) totally fixed the problem. Everything works like a champ now. Huzzah!