Bluepoint Design

Practical cost effective solutions   
RD login

Home
Up
Newsgroup post

9/16/2007 13:02 PDT:
When I attempt to log onto a server I get a broken Dialog box like this:

It started with a Windows Vista Ultimate laptop under my profile a couple of days ago when trying to connect to a clients RWW (Remote Web Workplace) using the ActiveX control but I was busy and didn't have a chance to mess with it. Instead I switched over to my desktop machine and it worked fine connecting the exact same way. But this morning when trying to log into the same place with a different profile on the laptop it failed the exact same way. Also the problem is there even when I use the regular Remote Desktop Client. I then went to my desktop machine which worked yesterday and it is now exhibiting the same problem. Yet another VU machine works flawlessly. 

Some facts:

bulletBoth client machines are running VU with all the more recent patches.
bulletThe failure occurs when trying to connect to Windows 2003 SBS servers using RWW of RD Client version 6.
bulletOther VU machines on the same network can still connect OK. Same version and build of the RD client.
bulletOn the affected machines I can connect to a Windows 2000 Server.
bulletIf I attempt to blindly enter a password it fails.
bulletCan log on to RWW and everything else works fine.
bulletIP address of hosting address recently changed.
bulletCan not move the dialog box around or interact with the box in any way.
bulletClose button on the window does not work. Eventually just crashes.
bulletReboot doesn't help
bulletClearing DNS cache doesn't help
bulletDeleting temp files doesn't help

9/16/2007 14:47 PDT:
An interesting transpiration. Consider machine A to be non-functional and B to be functional. There are no open TS sessions for the user on the TS. If I attempt a connection with machine A with proper credentials (see below about credentials) I get the problem above. But if I then connect with machine B I resume the disconnected session from my first attempt with machine A! This means that although it appears to have failed the first attempt in deed succeeded.

Now here's something funny with the credentials. The Windows domain is XYZ and the URL is mail.xyzcompany.com but when I go to connect it doesn't allow me to specify the user name and tells me I will be prompted later. But on machine B I can see that it will set the user name to mail.xyzcompany.com\user instead of just 'user' or 'xyz\user'.

9/16/2007 19:07 PDT:
Tried rolling back System Restore Points to as much as 2 weeks ago with no success on both machines.

9/18/2007 11:46 PDT:
When I use the same laptop with the same profile on site to directly connect to the servers it works fine! Hmmm....

9/19/2007 0907 PDT:
Got some suggestions from a guy in the newsgroup and logged in to check it out this morning on my desktop machine but tried to login first without making any changes. Worked the first time! I don't know what it was but it seems to have passed on it's own. Never got to try the old version of RDP or deleting the bitmap cache. Friday I'll confirm the laptop is OK too.

 

 
Practical cost effective solutions