Cannot connect to PC

  • Thread starter Thread starter Guest
  • Start date Start date
G

Guest

I am using 2003SBServer with XP workstations. My current problem is that I can't connect to one of my desktops via the Remote Desktop. All of the services are started and this is a "fresh install" I have checked that all the proper groups are added and I get the error message: "Client could not connect to the remote computer" The funny thing is that I can use Remote Desktop FROM this PC. I just can't log into it from another PC. I have no apps loaded on this computer yet, just XP that I JUST installed before connecting. Reformating and reinstalling can't be the only solution

Help please??
Ed
 
Have you checked on whether the ICF (Internet Connection Firewall) has been
activated in error on this machine?

Start, control panel, Network connections. Right-click the network
connection to the LAN, and click on the advanced tab. ICF is enabled by the
check box in the upper panel--You must either uncheck this, or click on
Settings, and enable remote desktop inbound traffic to pass through the
firewall.

Note: It may be a good practice to activate the firewall on all
workstations--even those behind a firewall. I don't know whether your
version of SBS 2003 has ISA firewall active, or simply the ICF firewall.
The ICF firewall's functionality will change significantly with SP2 for XP
and SP1 for Windows server 2003--but that's some ways off.
 
As much as I wanted that to be my solution. nopers. the ICF was disabled, i turned it on and alowed the Remote Desktop to pass through. Any other sugestions?
 
Can you ping the "bad" PC from any other machine?

If you share something on the "bad" PC--say, a CDROM drive---can you open
that share from another machine?

If you telnet to port 3389 on the "bad" machine, what response do you get?

You've stated that this is a fresh install, that "all the services" are
started. Is Terminal Services shown as started?

A repair install isn't as lengthy as the wait you've had for a response from
me, I'm afraid--that might be your best bet--reinstall XP over itself.
 
I know that would prolly cure my problems, but unless there is a bug in the RD system, this can't be my only option. Port 3389 is not open on the bad pc. Terminal Sevices is started and I have tried to renumber the port with regedt32 and had a interesting reaction. I changed it to 3390 and when i checked it with netstat -an it would show up, but is connected to my server. somthing like 192.168.0.10:3390 ESTABLISHED then when i changed it back it would not show up on the list. I will try a repair installation today and see if I can get anywhere. Thank
Edwar
..
 
I've seen anomalies from flawed installs, and some upgrade installs over
other OS's can result in policy settings that are unexpected. Your machine
appears to act as though there was a firewall installed--which doesn't make
sense given your descriptions.

Changes to RD like the port setting require a reboot to show--Terminal
Services can't be started and stopped.
(I'm not sure that explains your findings with the port change, but I
thought I'd mention it.)
 
I am rather fed up with this. I am just going to keep re-formating untill it works or untill I chuck the computer out the window and go build a new pc. Thank you for all your help
Ed Colema
www.colemancs.com
 
You might want to change some variable. Any chance you could try a
different video card or network card?
 
Back
Top