I connect to my SunBlade [on Solaris 9] using the keyboard/mouse provided by the sun. Now I would like to connect to it using my dell laptop running on Windows 7.
I have connected the laptop to the SunBlade using just a one crossover 9-pin connector [Without Router] using the free/basic version of the terminal client [AbsoluteClient].
But does not seem to work even though I have set the
AbsoluteClient hostname -> SunBlade ip addredd from /etc/hosts
AbsoluteClient port -> the port from /etc/services
Entries in /etc/services
---------------------
telnet 90/tcp
telnet 90/udp
I have also added the laptop ip address in /etc/hosts.
Can you ping the blade from the laptop -> No , Request Timed out error
Is the telnet service running (on port 90?) -> yes, it was 23, I changed to 90 in /etc/services
---------- Post updated at 09:29 PM ---------- Previous update was at 09:25 PM ----------
The question I have is, do I need a router or is a RJ45 [network cable] cable connection between laptop and the SunBlade be enough for a telnet connection ?
If it can talk to a router, it can talk to you instead. But you need to know what it's configured for and be on the same subnet, etc. This is all just basic networking.
Try port 23 again? I'm not sure /etc/services actually defines what port telnet uses.
You don't want or need a router, but you do need an Ethernet Hub or an Ethernet Switch which can handle the normal speed of the fastest interface. The cabling then would be two normal pin-to-pin RJ45 cables.
No reason to change the port for telnet - it only makes thing complicated.
From Windows 7, just try the supplied command-line telnet first before introducing 3rd-party software.
As Corona688 hinted, make sure that the IP addresses chosen are on the same IP network.
e.g. For a Class C private network.
192.168.10.4 with netmask 255.255.255.0
192.168.10.5 with netmask 255.255.255.0
No need for a router if they are on the same IP network.
Further to Corona688, the port definitions in /etc/services are purely documentary.
When I ping from my laptop to the sunblade ... I get the following output, it seems that the ping is fine....
C:\Users\xps1>ping 192.xxx.x.x
Pinging 192.xxx.x.x with 32 bytes of data:
Reply from 192.xxx.x.x: bytes=32 time=508ms TTL=64
Reply from 192.xxx.x.x: bytes=32 time=121ms TTL=64
Reply from 192.xxx.x.x: bytes=32 time=33ms TTL=64
Reply from 192.xxx.x.x: bytes=32 time=168ms TTL=64
Ping statistics for 192.xxx.x.x:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 33ms, Maximum = 508ms, Average = 207ms
I have to put the ip address and the port detail in the Telnet client. If I leave the port empty the connections fails. If I put 23, it still fails...
---------- Post updated at 10:41 PM ---------- Previous update was at 10:20 PM ----------
I tried the telnet and I get the following error
C:\Users\xps1>telnet 192.xxx.x.x
Connecting To 192.xxx.x.x...Could not open connection to the host, on port 23: Connect failed
I dont know where it has picked up the port 23 details.
---------- Post updated at 10:44 PM ---------- Previous update was at 10:41 PM ----------
As you understand that I am pretty new to all this, can you please confirm what you mean by "make sure that the IP addresses chosen are on the same IP network." ?
Do you now have a Hub or a Switch in the circuit?
Are your chosen IP addresses on the same IP network? It would be quicker to post the IP addresses and netmask values than to give an online course.
If you are familiar with arp -a quick check that the MAC address which is replying to ping is what you expect.
Corona688 makes a valid and very important point. The ping times for a locally connected computer should be near to zero or zero. Please pursue my suggestion to check that the computer which is replying is the correct computer.
I have done the telnet and the ping from the laptop
C:\>
C:\>telnet 192.168.0.4
192.168.0.4...:
C:\>ping 192.168.0.4
Pinging 192.168.0.4 with 32 bytes of data:
Reply from 192.168.0.4: bytes=32 time=232ms TTL=64
Reply from 192.168.0.4: bytes=32 time=356ms TTL=64
Reply from 192.168.0.4: bytes=32 time=78ms TTL=64
Reply from 192.168.0.4: bytes=32 time=334ms TTL=64
Ping statistics for 192.168.0.4:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 78ms, Maximum = 356ms, Average = 250ms
C:\>
Your ping times are the kind of ping times I see across a badly lossy wireless link! Over a loopback I'd expect 4 milliseconds or less, usually much less. Either something's very wrong with the cable or either card, or you're not talking to the machine you think you are.
Check arp /a on Windows, see if the MAC address you get for 192.168.0.4 matches the MAC address of the Solaris server's NIC. ( 0:3:ba:b:5e:b1 ? I've never seen a MAC address like that, does Solaris drop leading zeroes there or something?)