How do i set up two computers on the same network to RDC

[Zael]

I recently came to own a new computer, I've been using it for a while and set up Remote Desktop connection on it with a friends help. Now i'm going back to my old machine to try and set it up as a media server. Its not going to have a monitor connected to it so i need some way to connect and see whats going on.

Both machines are Win 7, although my old one is running 32bit.

I have a linksys e1200 router and both are wired connections. If you need more info please ask and i'll do my best to answer it.

I need help connecting it to the network so i can remote into it. I've set it up as best i could but it still wont allow me to connect. I think i'm missing something but whatever it is alludes me

 

[The Howling Wolves]

Have you tried Network Sharing..
Look at Doc's suggestions #2 and #3
http://www.sevenforums.com/network-sharing/125577-setting-up-home-network.html

Hope this is what you are looking for!
THW

 

[Zael]

Alright i am set up for the network. Now i'd like to be able to Remote into it. I can do it from my Old PC into my new one but not the other way around.

Thanks for the other link by the way, it was very helpful.

 

[The Howling Wolves]

Standard Windows workgroup based sharing requires that you have users with the same name present on both systems and that the named user on the sharing system has sufficient NTFS permissions on the shared files to perform the actions required by the remote user.

 

[Solidwave]

Alright i am set up for the network. Now i'd like to be able to Remote into it. I can do it from my Old PC into my new one but not the other way around.

Thanks for the other link by the way, it was very helpful.

Remote desktop is usually pretty close to foolproof.

Did you enable remote access, in control panel, on the old PC?

What error messages do you get when you try to connect into the old PC?

 

[Zael]

Yes I did. And it gives me the error saying that the computer is not on, or accepting rdc which rdc is turned on.

 

[Solidwave]

Can you see the old PC on the new PC's list of networked computers? (e.g. under 'network' in the left pane of any folder)

What happens if you ping it? (Press, winkey-R, type CMD, press enter, type ping [name of machine], press enter.)

If the old PC is running any third party firewall software did you define a rule for remote desktop (port 3389)?

 

[Zael]

Yeah i can see it. I can ping it I have the port open to 3390 due to 3389 being taken by my new computer and it coming up with an overlapping error whenever i try to do 3389. All my firewalls are disabled. I used to run RDC on it when it was the only PC i had but now i can't seem to connect to it at all. Only my new one. Ive tried <xxx.xxx.xxx.xxx:3390> but it doesn't work still. it just times out with the 1)remote access to the server is not enabled 2)The remote computer is turned off and 3) The remote computer is not available. Which it is to all three.

 

[Solidwave]

I'm not sure what you mean by an overlapping error. Listening port numbers are only unique to each individual computer, not to the entire network. Unless you're forwarding remote desktop traffic through your router--which you only need to do if you're accessing your computers remotely via the Internet--you can have remote desktop listen on port 3389 on both computers.

Try resetting old PC to listen on 3389.

Can you run "netstat -a -b -p TCP" at an elevated command prompt on the old PC and post the results? This will show what services are listening on what ports to see if remote desktop is listening where it should be or not.

 

[Zael]

C:\Windows\system32>netstat -a -b -p tcp

Active Connections

Proto Local Address Foreign Address State
TCP 0.0.0.0:135 S1211:0 LISTENING
RpcSs
[svchost.exe]
TCP 0.0.0.0:445 S1211:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:554 S1211:0 LISTENING
[wmpnetwk.exe]
TCP 0.0.0.0:2869 S1211:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:3389 S1211:0 LISTENING
CryptSvc
[svchost.exe]
TCP 0.0.0.0:5357 S1211:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:10243 S1211:0 LISTENING
Can not obtain ownership information
TCP 0.0.0.0:49152 S1211:0 LISTENING
[wininit.exe]
TCP 0.0.0.0:49153 S1211:0 LISTENING
eventlog
[svchost.exe]
TCP 0.0.0.0:49154 S1211:0 LISTENING
Schedule
[svchost.exe]
TCP 0.0.0.0:49156 S1211:0 LISTENING
[lsass.exe]
TCP 0.0.0.0:49157 S1211:0 LISTENING
[services.exe]
TCP 127.0.0.1:5354 S1211:0 LISTENING
[mDNSResponder.exe]
TCP 127.0.0.1:5354 S1211:49155 ESTABLISHE
[mDNSResponder.exe]
TCP 127.0.0.1:5357 S1211:49171 TIME_WAIT
TCP 127.0.0.1:5357 S1211:49222 TIME_WAIT
TCP 127.0.0.1:27015 S1211:0 LISTENING
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:27015 S1211:49161 ESTABLISHE
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49155 S1211:5354 ESTABLISHE
[AppleMobileDeviceService.exe]
TCP 127.0.0.1:49161 S1211:27015 ESTABLISHE
[iTunesHelper.exe]
TCP 127.0.0.1:49240 S1211:2559 SYN_SENT
[nvtray.exe]
TCP 192.168.1.243:139 S1211:0 LISTENING
Can not obtain ownership information
TCP 192.168.1.243:2869 192.168.1.1:1333 TIME_WAIT
TCP 192.168.1.243:2869 192.168.1.1:1334 TIME_WAIT
TCP 192.168.1.243:2869 192.168.1.1:1339 TIME_WAIT
TCP 192.168.1.243:2869 192.168.1.1:1340 TIME_WAIT
TCP 192.168.1.243:2869 192.168.1.1:1343 TIME_WAIT
TCP 192.168.1.243:2869 192.168.1.1:1344 TIME_WAIT
TCP 192.168.1.243:2869 Z-CRIM-24:54753 TIME_WAIT
TCP 192.168.1.243:2869 Z-CRIM-24:54754 TIME_WAIT
TCP 192.168.1.243:2869 Z-CRIM-24:54755 ESTABLISHE
Can not obtain ownership information
TCP 192.168.1.243:5357 Z-CRIM-24:54800 ESTABLISHE
Can not obtain ownership information
TCP 192.168.1.243:49160 LB240:http ESTABLISHE
[ConduitHelper.exe]
TCP 192.168.1.243:49162 Z-CRIM-24:netbios-ssn TIME_WAIT
TCP 192.168.1.243:49164 Z-CRIM-24:netbios-ssn TIME_WAIT
TCP 192.168.1.243:49166 nuq04s06-in-f3:http ESTABLISHE
[ConduitHelper.exe]
TCP 192.168.1.243:49172 Z-CRIM-24:icslap ESTABLISHE
[wmpnetwk.exe]
TCP 192.168.1.243:49190 192.168.1.1:1780 TIME_WAIT
TCP 192.168.1.243:49192 192.168.1.1:1780 TIME_WAIT
TCP 192.168.1.243:49194 192.168.1.1:1780 TIME_WAIT
TCP 192.168.1.243:49205 logitech:http TIME_WAIT
TCP 192.168.1.243:49206 logitech:http CLOSE_WAIT
[LogitechUpdate.exe]
TCP 192.168.1.243:49211 logitech:http TIME_WAIT

 

[Zael]

I'm sick and tired of the machine so i'm going to Reinstall the OS and try again. Who knows, it might work.

 

[metalmania31]

All PC's are win7 pro? Home cannot do RD with the built in RD.

 

[jeepmann4x4]

It's not really a Fix to your issue but you could always use a third-party program if you can not get it worked out.

TeamViewer

Home use is free and it can be setup to start with Windows.

 

[AllOnTheBus]

All PC's are win7 pro? Home cannot do RD with the built in RD.

That was my next question - there is a difference between
Remote Access and RDC - Windows version could be the issue.