I would like to open a PuTTY terminal session on one machine which is physically connected to another machine via an ethernet cross-over cable. Ideally characters entered in the PuTTY terminal window on one machine would appear in the terminal window on the other machine.
Is this possible?
Hardware & Configuration:
I disabled wireless adapters on each machine and went to: Control Panel / Network and Internet / Network and Sharing Center / Chose Local Area Connection / Properties / Select TCP/IPv4 / Chose Properties button and set the addresses accordingly. Settings common to each machine were:
- Subnet Mask: 255.255.255.0
- Default Gateway: 192.168.1.0
- Preferred DNS Server: 18.104.22.168
- Alternate DNS Server: 22.214.171.124
Machine 1: Windows 7, 64-bit, SP1. Static IP address is 192.168.1.4
Machine 1: Windows 7 (embedded), 32-bit. Static IP address is 192.168.1.5
Both machines have had their Windows Firewalls disabled.
I lied when I said the devices were physically connected via an ethernet cross-over cable. Rather, each machine is connected to an ethernet/RF modem (have been assigned the static IP addresses 192.168.1.2 and 192.168.1.3) via a standard network cable. The modems should be transparent, so for all intents and purposes the two machines should be connected via ethernet.
Approach & Attempts at Solution
On each machine, at the command prompt, I can ping each of the following IP addresses. 192.168.1.2, 192.168.1.3, 192.168.1.4, 192.168.1.5. Confirmed. We see small ping transmission times associated with the local ethernet adapter IP address and local modem, longer times associated with the transmission to the IP addresses on the other side of the RF link.
I do: Search / choose Network / and see two and only two computers on each machine.
On both machines, I launch a PuTTY session, choose SSH, enter the appropriate IP address (192.168.1.5 from 192.168.1.4 and vice-versa) and use the default port value of 22. I also disable authentication (not sure if this makes any difference) by going to SSH / Auth / and choose bypass authentication entirely. When I attempt to launch the PuTTY session, I get the Network error: Connection refused message. Confirmed.
So then I ask the question: How do we know that port 22 is the right port number? I go to the opposite machine, at the command prompt type: netstat -a. I see the following:
a. Under TCP protocol, and LISTENING state I see 0.0.0.0:7, 0.0.0.0:9, etc. for port numbers 7, 9, 13, 17, 19, 80, etc. No port 22 is observed.
b. Also under TCP protocol, and LISTENING state I see 192.168.1.5:139. This strikes me as the most encouraging port number to try connecting through/over. It turns out that both machines are of state LISTENING on port 139.
c. Further down the list under UDP protocol, but with the state field un-populated, I see 192.168.1.5:137, 192.168.1.5:138, etc. for ports 137, 138, 520, 5353.
Next I try going back to establishing a connection in PuTTY, this time using port 139. This time I get the message Network error: Software caused connection abort. The error presents itself 30 s or so after attempting the connection. I do the same from the other machine and get the message: Network error: connection timeout.
If I run netstat -a at the command prompt shortly after trying to connect to the other machine in PuTTY, I saw an entry (Protocol | Local Address | Foreign Address | State) which was
TCP | 192.168.1.5:49328 | 126.96.36.199:netbios-ssn | SYN_SENT
And have seen a state value of ESTABLISHED where the foreign address corresponds to the machine I was trying to establish the connection with.
I guess, firstly, I'll re-iterate the central question:
Can I send characters from one terminal session/machine to the other in this way?
If so, any thoughts and/or comments on how to establish a reliable connection would be greatly appreciated.