Hello,
I've seen this several times in the archives, but never have I seen a real solution. There was mention of a fix in version 4.1, but we are running 4.1.1 and we are getting this problem, so they must not have implemented a solution. We are running RDP from time to time, but I don't understand why this is still causing a problem because we had it running fine in a test environment before deploying it. It is a Windows 2003 server with very little installed. We also have a Windows XP computer that we have at the same site that I just tried to connect to and got the same error message. We are not running RDP on that computer at all and never have. I saw a couple of suggestions for a work around such as tscon 0 /dest:console but this did not work because the RDP session was not 0 and the console was already logged in to session 0. I also saw something talking about mstsc.exe /console and I tried working with that but it also did not work. We are connecting through a point to point VPN using Cisco PIX firewalls. Everything from one internal network to another is explicitly permitted, and the PIX config is basically identical to all of the other sites, so I don't think that it would be causing any problems. Like I said, we have had this computer in a test environment where we ran both VNC and RDP for a week and a half without any problems whatsoever, and then when we deployed it we started having issues. We also have several other sites where we run RDP and VNC together where we have not had any problems. In fact, two of the sites have identical hardware and install images. Does anyone have any ideas as to what else could possibly be causing this? I appreciate any suggestions, _____ Benjamin Jitima Forth Foods [EMAIL PROTECTED] (304) 617-5806 _______________________________________________ VNC-List mailing list [email protected] To remove yourself from the list visit: http://www.realvnc.com/mailman/listinfo/vnc-list
