01-22-2012
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.
Last edited by allenhibbert; 01-22-2012 at 07:59 PM..
10 More Discussions You Might Find Interesting
1. HP-UX
Hi, Haveing a little trouble with data protector (5.5) on HP-UX (11.11, 11.23)
under Xwindows Chameleon UNIX 97 (7.0 - its a old version)
I am trying to get the GUI for DP up and running on a HP-UX cell manager and I have the following problem.
The GUI starts up with no errors that I can... (2 Replies)
Discussion started by: Andrek
2 Replies
2. Solaris
Hello.
I had installed solaris 10 in morning , and all was running fine... I just logged out and logged in with another user ID oracle - It got stuck and then I pressed the button for restart.
Now I see only word GRUB written in top line rest everything is black.
What to do? (2 Replies)
Discussion started by: panchpan
2 Replies
3. Solaris
Hi All,
I have a solaris machine that powers up and displays a blank screen?
All the keyboard, monitor and mouse are plugged in. It was booting fine before and when it was disconnected and re-connected (mouse/keyboard/monitor) it just powered on and came up with a blank screen.
Please... (5 Replies)
Discussion started by: tlee
5 Replies
4. Solaris
Hello
I'm new in sun and i have a liitle problem.
I buy sun enterprise 420r and connect keyboard and monitor crt (non Sun).
But when i start server i have blank screen on crt. I'm new in sun servers and i dont know why its doin this. (11 Replies)
Discussion started by: elmik
11 Replies
5. Shell Programming and Scripting
Dear Member,
OLD Question --> disable-completion not solved
My bash Menu script ping process problem.
If ping still running and users press SCREEN is Blank...
Cant Members help me.. kill signal or others scripting for my case, btw i use Linux..
Thanks,
Rico
My Bash Script :
... (1 Reply)
Discussion started by: carnegiex
1 Replies
6. Solaris
I have a SunFire V490
Recently when the server is rebooted the screen goes blank from when the CDE is shutdown to when it is started up again.
Has anyone got any ideas what might be causing this?
I've had a quick look in messages but can't find anything in there. I've had a look at... (2 Replies)
Discussion started by: sonic72
2 Replies
7. Ubuntu
Hello,
I got blank screen when reboot after I tried to upgrade Ubuntu (64 bit server version) from 11.10 to 12.04 at update manager.
The normal login GUI is missing, but mouse cursor is fine. Then I switched to terminal (tty1 ~ tty6), which looked fine and showed it is Ubuntu 12.04 ! (Forgot how... (4 Replies)
Discussion started by: yifangt
4 Replies
8. Solaris
we are using sun solaris sunfire v445, yesterday improperly shutdown the server
and now while restart the system show a screen which is blank and the hard disc drive indicator light is also not glowing. (10 Replies)
Discussion started by: mrdb
10 Replies
9. HP-UX
Hi,
I have this Unix script that kills a user session. When I run it, my screen goes blank. How do I prevent the blank screen?
Ex: I open 2 Unix sessions. The main PID for my 1st session is 1234. In the second session I issue a "kill -HUP 1234". The first session gets killed but the second... (5 Replies)
Discussion started by: rm-r
5 Replies
10. UNIX Desktop Questions & Answers
Hi all, I'm running CentOS 7. When the machine is left alone for a few minutes, a screen saver or blanker or something comes up with a clock and date on it. You have to swipe this to get back to the desktop. I'm trying desperately to get rid of this so that it never comes up. No matter how long... (1 Reply)
Discussion started by: marmotking
1 Replies
telnetd(8) System Manager's Manual telnetd(8)
NAME
telnetd - The DARPA telnet protocol server
SYNOPSIS
telnetd [-debug [port]] [-D modifier ...]
FLAGS
Starts telnetd manually, rather than through inetd, on alternate TCP port number port (if specified). Prints out debugging information.
modifiers are: Prints information about negotiation of telnet options Same as options with additional processing information Displays the
data stream received by telnetd Displays data written to the pty Not yet implemented
DESCRIPTION
The telnetd daemon is a server that supports the DARPA (Defense Advanced Research Projects Agency) standard telnet virtual terminal proto-
col. telnetd is invoked by the Internet server (see inetd(8)) normally for requests to connect to the telnet port as indicated by the
/etc/services file (see services(4)). The -debug flag may be used, to start up telnetd manually. If started up this way, port may be
specified to run telnetd on an alternate TCP port number.
The -D options may be used for debugging purposes. This allows telnetd to print out debugging information to the connection, allowing the
user to see what telnetd is doing.
The telnetd daemon operates by allocating a pseudoterminal device (see pty(7)) for a client, then creating a login process that has the
slave side of the pseudoterminal as stdin, stdout, and stderr. telnetd manipulates the master side of the pseudo-terminal, implementing
the telnet protocol and passing characters between the remote client and the login process.
When a telnet session is started up, telnetd sends telnet options to the client side, indicating a willingness to do remote echo of charac-
ters, to suppress go ahead, to do remote flow control, and to receive terminal type information, terminal speed information, and window
size information from the remote client. If the remote client is willing, the remote terminal type is propagated in the environment of the
created login process. The pseudoterminal allocated to the client is configured to operate in cooked mode, and with XTABS and CRMOD
enabled (see tty(7)).
The telnetd daemon is willing to do: echo, binary, suppress go ahead, and timing mark. telnetd is willing to have the remote client do:
line mode, binary, terminal type, terminal speed, window size, toggle flow control, environment, X display location, and suppress go ahead.
The telnetd daemon never sends telnet go ahead commands.
Note that binary mode has no common interpretation except between similar operating systems (Unix compatible systems in this case).
Note also that the terminal type name received from the remote client is converted to lowercase.
The telnet command uses the default Type-of-Service value recommended by RFC1060, which is as follows: Low delay
You can configure this value by specifying it in the /etc/iptos file. For more information, see iptos(4).
By default, the telnetd daemon starts the login dialog using the login string specified in the message field of the /etc/gettydefs file.
If you want to use a customized banner, create an /etc/issue.net or /etc/issue file. The telnetd daemon reads the file that exists and
writes its contents over a new telnet connection prior to starting the login dialog. If both files exist, only the /etc/issue.net file is
used.
CAUTIONS
Some telnet commands are only partially implemented.
Because of bugs in the original 4.2BSD telnet(1), telnetd performs some dubious protocol exchanges to try to discover if the remote client
is, in fact, a 4.2BSD telnet(1).
FILES
Specifies the command path. Specifies the path name for the network issue identification file. Specifies the path name for the issue
identification file.
RELATED INFORMATION
Commands: telnet(1).
Files: iptos(4), issue(4), issue.net(4). delim off
telnetd(8)