Gentlemen, I've tried extremely hard to hookup my notebook via the hyperterminal to my AIX box (IBM 7046-B50) by virtue of a cross-over cable. Don't know really whats going on ......to my surprise. The notebook says its hookedup successfully but shows no unix login prompt on the hyperterminal console.
I honestly suspect that there's something wrong with the STATIC IP's that I'm typing for the TCP/IP settings or maybe the DNS IP's for Windows XP which might be causing this every irritating problem anyhow thats my opinion can anyone of you suggest to me the right approach here. Will be extremely grateful for that.
NOTE: Not getting any responses while trying to ping the server too.
What is the IP address of the AIX system?
What is the IP address of the notebook?
If you have DHCP on the notebook is the AIX a DHCP server?
Can you ping the notebook from the server?
This is a SERIAL line, there is no IP adress involved.
Set your terminal emulator to 8N1, 9600 (thanks to dukessd i have finally managed to remember the correct settings - thanks ) and enable "hardware handshake" (RTS/CTS) flow control. Set the terminal to "wyse60" if possible or to "vt100", but definitely not the "ansi" crap the Windoze terminal emulators usually offer as default.
Maybe you will have to use another cable too, what you need is a "nullmodem" cable, like the one packaged with the Laplink software. You could, of course, also order one from IBM (this option is for the stinking rich, but guaranteed to be working).
Just fired up hyper-term on a pc with win2k and no serial ports and it asked for the ip address and shows default port 23!
Well I never!
Anyway, bakunin, sure does look like he is using ip not serial and as an aside I don't think IBM will sell you such a cable because they do not make one - or more correctly they do not know they sell one.
Well, not for connecting a 9 pin terminal to an rs6k, although I believe the ESS / Shark cable the CEs use for servicing the old 2105 is just the job, if only I knew the part number...
For PC to RS6k / pseries / system p connection using a 9 pin d-type at both ends the cable you need is as follows:
If you are using fixed IP on the B50 you will need to configure your laptop to use a fixed IP address in the same subnet as the B50 before the connection will work.
My bad, i didn't know that Hyperterm also supports IP connections. In case it is an IP connection dukessd is of course right: the subnets have to be matching.
The serial cable can indeed be ordered. Actually i did that in my last project, because my the project manager didn't want to use a cable soldered together by my colleague. It costed about 70 Euros (~100 Dollars), but it worked.
) and enable "hardware handshake" (RTS/CTS) flow control. Set the terminal to "wyse60" if possible or to "vt100", but definitely not the "ansi" crap the Windoze terminal emulators usually offer as default.