Port connection error

[unix adm]

Hi

I have one port open (65534) for running some applicaion.

However when I m trying to connect it form the same server it self..

XXXXX@XXXXXXX$ telnet localhost 65534
Trying...
Connected to localhost.
Escape character is '^]'.

connecting fine


However when I m trying to connect

XXXXX@XXXXXXX$telnet servername 65534
root@bze2uo02# telnet bze2uo02 65534
Trying...
Connected to bze2uo02.
Escape character is '^]'.
’PuTTY

giving some junk charactor. This is from the same server.


This was working fine before can somebody help..please

Thanks
Rajeev

[Ivan Ferreira]

What is doing the "PuTTY" string there? Try using the full path to the telnet command, in case is "aliases" to other emulation program:

/usr/bin/telnet servername 65534

[Steven E. Protter]

Shalom Rajeev,

What was the response before the junk characters?

What has changed?

Check and see if the application daemon is running.

SEP

[unix adm]

Hi Ian

Full path name still doesn't help..

Hi SEP,

Apps daemon is running it is perl script being triggered by inet services. We tried restarting inet services. Still it does not help. Earlier it was coming like this


/usr/bin/telnet localhost 65534
Trying...
Connected to localhost.
Escape character is '^]'.

1st line must be RequestType:[reqeust type], however you supplied: ''.
ERROR-CM_INFO_BEGIN
FatalError
CM_INFO_END
CM_ERROR_BEGIN
1st line must be RequestType:[reqeust type], however you supplied: ''. at /home/ccadmin/cmserver/Wolf/CM/ResponseHandler.pm line 42, line 1.
CM_ERROR_END


Thanks
Rajeev

[Ivan Ferreira]

Try with:

stty sane

What if you do this directly from the console? Maybe is just your terminal emulator.

[Mark Greene_1]

The "PuTTY" is the answer-back to a control-E and the default value from the PuTTY application. Change your session to reply with vt100 or whatever emulation you are using. I'm guessing that the .profile for the login ID you are using is executing a tset to establish the terminal type.

mark

[A. Clay Stephenson]

You have made a poor choice for a port number. Ports in the range 49152-65535 are in the anonymous or private range. These ports should be assigned by the system automatically after a connection has been established on another port. You should really pick an unused in the range 1024-49151 that is listed by www.iana.org as available or unused.

[unix adm]

We got to restart the server and its working fine now. Problem what seems to me was..inetd daemon was beeing restarted ..under some activity..


Thanks

[unix adm]

Thanks to every body for there responce


Rajeev