Link to home
Start Free TrialLog in
Avatar of intelogent
intelogentFlag for United States of America

asked on

Can not connect with Remote desktop

hi,

i just brought a new win  & system into my office as a workstation.
i have a server running win server 2003.  we regularly connect to it all day long using remote desktop and specify it's ip address.  " 192.168.1.2 "
however, my new workstation can not connect to the server. My old one has no problem. I do not even get the oppurtunity to log on to the server.  as soon as i try to connect, i just get an immediate message.. " this computer can not connect to the remote computer. "

we are in the same office, and not needing to go out throuh the internet.   however, this new workstation has no problem connecting to the internet... and we are all on the same network.

any ideas.
ASKER CERTIFIED SOLUTION
Avatar of saastech
saastech
Flag of United States of America image

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of intelogent

ASKER

yes i can ping the server...
and yes i am using term server....
Is your new workstation on the domain?
no domain.... we are peer to peer
Can you connect remotely to any other computers in your network?
SOLUTION
Avatar of Ravakl
Ravakl

Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
@saastech could be right.

You are able to limit connections to the TS through a GPO or under the TS Configuration (Right click RDP-Tcp, click properties go to Network Adapter tab)

Either of those places, depending on your configuration, you can limit the amount of simultaneous connections.
none of the above...

i can ping it...
i can type \\192.168.1.2 from run and see the shares
just can not use remote desktop to connect.   and terminal services are running jost fine.

let's keep trying... we will get it
Can you connect RDP to any other machine?
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
closed windows firewall on the workstation.... and still it will not connect. however, it does connect to other machines on my VPN... this one server is local, and we can not connect to it
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Now that I got that silly question out of the way, is the terminal service port filtered or blocked. A quick way to tell is go to the command prompt and type:

portqry -n 192.168.1.2 -p TCP -e 3389
i am not in my office again till monday.
but, if one machine in the office can get in, and the others can not... and they are all simply using RDP, can the port be considered a culprit...
also, i regularly RDP into this particular server from outside my office accross the internet..
it is my beleif that the conflict exists between the two machines.....

but i will check first thing monday morning.
SOLUTION
Link to home
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Start Free Trial
Avatar of Ravakl
Ravakl

What Windows version is installed on the new PC?
Ravaki

excellent idea... i will not be in my office again till Thurs mirning.. but i absolutely will ...
fortunately, it is the backup server, and the main server is back on line... but i still need to resolve this.
funny, i had a back up server built to spport 5 locations... and the only location that was having difficulty was mine...   go figure.....
but i am not going to let the problem go.
You are implying that RDP worked before. Service pack II had problems with Terminal Services and RDP because it changed the listening port  of RDP. Details are listed on this thread.

https://www.experts-exchange.com/questions/23577994/We-just-recently-started-having-an-issue-with-remote-desktop-we-can-logon-as-local-admin-but-not-domain-admin-the-screen-hangs-and-never-logs-in.html
the issue was that   both the server... and a printer shared a static ip address.. hence the lan users we denied access...

had no effect ont he wan users.

interesting   isn't it.