• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

RDP issue with Windows XP

V

VinylxScratches

Golden Member
I Remote into my Windows XP machine from my Macbook which uses 10.5 Leopard. I'm using CoRD and Microsoft's RDP solution.

I can't RDP into my computer until I physically login to my Windows XP machine. Then I can RDP into it. Is that how it's supposed to work? It's a bit annoying because I'm trying to make my PC headless and I have to switch my monitor and use my other keyboard just to initially log in.
 
Originally posted by: VinylxScratches
I can't RDP into my computer until I physically login to my Windows XP machine. Then I can RDP into it. Is that how it's supposed to work?
Click to expand...
Nope. RDP is a service and should be running whether somebody is logged in or not. Are you having a problem with hibernation or other low-power mode?
 
I've ran into similar problems with Remote Desktop at machines at work. Even though both machines are running XP Pro 32, I need to physically log into the machine I want to RD into before I can remote into the machine from my desk. Typically, its not a major problem because usually these machines are in our image lab and just need some updating to make them 'production' ready. I just prefer to RD into them so I can work on other tasks while I'm preparing the other machines.
 
Does the account your trying to remotely login to have a password? You can't login through remote desktop if the password is blank for security reasons unless you change a registry setting / group policy setting.
 
OK, so when you try to log in over RDP, how far does it get? Any error messages?

If you telnet to your XP box, is it listening? At the Command Prompt:
"Telnet mybox 3389" --- (where mybox is the name of your XP box)
If the XP box is listening on TCP Port 3389, then the Command Prompt screen will go blank. If the XP box isn't litening or a firewall is blocking it, there'll be a "Could not open connection to the host on port 3389" message.
 
I guess I don't have any issues RebateMonger. Just that I'm impatient! I tried telneting and it worked so then I tried to RDP and it worked. I guess it takes a bit of time for the XP box to load all services.

Thanks!
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top