xp to aix - telnet blank screen

hello,

i am trying to test connection to a 5.3 box. from an xp machine, telnet connects but shows only a blank screen. cursor moves as i type, but no response back.

have used telnet, putty and accuterm - all same result
verified that telnet services are active in xp
xp windoze firewall is off - service not started
set norton on the xp box to accept any protocol traffic from 5.3 box
verified that router is not blocking telnet or comms between the systems
verified that telnet services are active in 5.3
verified that aix is listening on port 23
verified inetd.conf, services and rc.net all look good

i can ping the 5.3 box from xp
i can ping the xp box from 5.3

telnet from the 5.3 box works to the xp machine - receive a logon
telnet from the xp machine to 5.3 connects, shows no logon or other characters

netstat -an|pg on the 5.3 box while telnet from the xp machine shows that the connection is established on port 23 on 5.3 box and port 3100 on the xp machine

any suggestions or info. on what i may be missing so that i can telnet from the xp machine to the 5.3 box and login successfuly is appreciated. once i can confirm this, i'll look into an ssh connection.

try telnet on to localhost on the AIX box to see if you do not have problems with telnet service on your server

Check that the router does inbound NAT for port 23 to 3100

Can you wait more than two minutes and see if a login prompt appears?

thanks for the replies

gito - yes, i had tried that and was able to do the localhost telnet - sorry did not mention that

frank - yes, I waited approx 15 minutes to rule out any negotiating delays and to see if it would time out - which it did - i also have the system set to timeout for inactivity

jgt - nat is enabled on the router - however, i did/do not see options for specific ports or a range of ports - i'll dig some more on that

1) Are you able to post the output from this command from BOTH computers, making it clear which is AIX and which is M$:

netstat -rn

2) Long shot
If the XP computer is a laptop and this is a wired LAN connection, make sure that the wireless is disabled.

3) Even longer shot
Whether disabled or not the Microsoft Windows XP Firewall is omnipresent. Enabling "telnet" on a totally disabled Microsoft XP Firewall could well do the trick. I've seen it work with FTP connections.

hey methyl,

xp machine is not a tower/desktop
yea - i've experienced the same where a disabled windows firewall is disabled but still mucking up connectivity - i set it to allow for telnet, no change

here are the results from netstat -rn for each system

aix 5.3 box
netstat -rn

Routing tables
Destination           Gateway            Flags         Refs             Use       If        Exp    Groups

Route Tree for Protocol Famil 2 (Internet):
default               192.168.1.1        UG              0                 2      en0        -         -
127/8                 127.0.0.1          U               5               106      lo0        -         -
192.168.1/24          192.168.1.105      U               1                 5      en0        -         -       =>
192.168.1/24          192.168.1.106      U               1                 1      en1        -         -
192.168.1.101        192.168.1.1       UGH             0                58      en0        -         -
192.168.1.105        192.168.1.106   UHSb           0               365      en1        -         -       =>
192.168.1.105         127.0.0.1          UGHs            1               714      lo0        -         -
192.168.1.106         127.0.0.1          UGHs            0                 1      lo0        -         -
192.168.1.255         192.168.1.105      UHSb            0                 4      en0        -         -

Route Tree for Protocol Family 24 (Internet v6):
::1                   ::1                UH              0                 0      lo0        -         -
xp machine
netstat -rn

Route Table
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x2 ... ...... Realtek RTL8169/8110 Family Gigabit Ethernet NIC
 - Packet Scheduler Miniport
0x3 ... ...... Juniper Network Connect Virtual Adapter - Packet
 Scheduler Miniport
===========================================================================
===========================================================================
Active Routes:
Network Destination        Netmask          Gateway       Interface  Metric
          0.0.0.0          0.0.0.0      192.168.1.1   192.168.1.101       10
        127.0.0.0        255.0.0.0        127.0.0.1       127.0.0.1       1
      192.168.1.0    255.255.255.0    192.168.1.101   192.168.1.101       10
    192.168.1.101  255.255.255.255        127.0.0.1       127.0.0.1       10
    192.168.1.255  255.255.255.255    192.168.1.101   192.168.1.101       10
        224.0.0.0        240.0.0.0    192.168.1.101   192.168.1.101       10
  255.255.255.255  255.255.255.255    192.168.1.101   192.168.1.101       1
  255.255.255.255  255.255.255.255    192.168.1.101               3       1
Default Gateway:       192.168.1.1
===========================================================================
Persistent Routes:
  None

Looks like the AIX box has two interfaces, both with IP addresses on the same network. As somebody pointed out in a post not too long ago, this is invalid.
Which IP address is the PC trying to connect to?

There are some very strange static routes too.

Perhaps an AIX comms specialist can explain what is going on here.

2 cards - each has its own ip - one broadcasts to the other

trying to connect to 192.168.1.105

Why would this be invalid?

---------- Post updated at 20:23 ---------- Previous update was at 20:16 ----------

while logged into the AIX server can you test the following.

telnet 192.168.1.105
telnet 192.168.1.106

If this works run the same test on different workstation/server the same network. If that succeeds I would focus on the router configuration.

hey - thanks for all the replies/help. i got it now.

frank - i could telnet to 192.168.1.106 - but, 105 worked at first, today gave me a permissions error; obviously i had changed something earlier in the game.

so, i started from scratch and everything looked good. then i spotted a static route in rc.net to the default gateway, which i must have added before. once i commented that out, since it is already set in en0 and en1, the telnet worked both on the system and from the outside client.

its good now - thanks again!

  • sig tag -
    5 days a week i travel to planet htrae, where i strive to protect my system from the inhabitants