Telnet to ThinkBlue 7.1a

Discussion:

sarn756

2005-06-03 21:44:48 UTC

Folks,

I am sure that this question has been asked, but I have been
unable to find any references out on the archives.
I am running Windows 2K(at 192.168.7.47), the latest Cygwin
(downloaded 5/31/2005), WinPCap 3.0, TunTap32 2.0.3.379, FishPack
1.3.0.323, and Hercules 3.02.
I nrought up Hercules with V</370 to verify my Windows set up and
all was well. I am now attempting to install ThinkBlue Linux for
z/Series 7.1a.
I get to the point in the install, where it says to telnet into
the machine to continue the install and I hit a brick wall. I have
tried telnet from a cmd shell, I have tried it from Reflections, and
I have tried it from puTTY with no luck. Any help here would be
greatly appreciated.

I have a CTC connection defined as follows:

0620-0621 3088 CTCI -n 00-0D-56-E0-C2-EE 192.168.7.244 0.0.0.0

When I start up Hercules, I see the following:

TunTap32.dll version 2.0.3.379 initiated
HHCCT073I 0620: TUN device tun0 opened

ThinkBlue is able to activate the CTC0 adapter at 0620/0621 and I
am able to ping my Win2K system from ThinkBlue and I can ping
ThinkBlue from Win2K(.ping 192.168.7.47 on Herc console).
At IPL, I see the following from the bootstrap loader:

Linux version 2.4.7-0.24.23BOOT (root-FSNxZbiF/o/***@public.gmane.org) (gcc version
2.95.3 2001
0319 (prerelease Red Hat Linux S/390)) #1 SMP Mon Oct 8 15:44:26 CEST
2001

My answers to ThinkBlue are as follows(and, yes, I saw the
SIOCADDRT message):

FQDN - .linux390.company.com
Network device - .ctc0
IP address of VM - .192.168.7.244
IP address of ctc partner - .192.168.7.47
CTC device address - .auto
The response from Herc is:
CTC driver Version: 1.49 initialized
ctc0: read: ch 0620 (irq 0017), write: ch 0621 (irq 0018) proto: 0
ctc0: connected with remote side
SIOCADDRT: No such device
ctc0 Link encap:Serial Line IP
inet addr:192.168.7.244 P-t-P:192.168.7.47
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MTU:32760 Metric:1
RX packets:86 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0
carrier:0

sarn756

2005-06-08 19:26:17 UTC

Permalink

I never got a response on the problem below, but I would like to
throw in another bit of information. I brought up Herc 3.02 on a
Fedora Core 3 machine at home last night and was able to telnet into
the ThinkBlue installation with no problems using the same
configuration file(just different platform).

So the question still exists as to why I can ping the ThinkBlue Linux
across the CTC connection, but I cannot telnet to it using puTTY,
Reflections, or Windows command line telnet.

Post by sarn756
Folks,
I am sure that this question has been asked, but I have been
unable to find any references out on the archives.
I am running Windows 2K(at 192.168.7.47), the latest Cygwin
(downloaded 5/31/2005), WinPCap 3.0, TunTap32 2.0.3.379, FishPack
1.3.0.323, and Hercules 3.02.
I nrought up Hercules with V</370 to verify my Windows set up and
all was well. I am now attempting to install ThinkBlue Linux for
z/Series 7.1a.
I get to the point in the install, where it says to telnet into
the machine to continue the install and I hit a brick wall. I have
tried telnet from a cmd shell, I have tried it from Reflections, and
I have tried it from puTTY with no luck. Any help here would be
greatly appreciated.
0620-0621 3088 CTCI -n 00-0D-56-E0-C2-EE 192.168.7.244

0.0.0.0

Post by sarn756
TunTap32.dll version 2.0.3.379 initiated
HHCCT073I 0620: TUN device tun0 opened
ThinkBlue is able to activate the CTC0 adapter at 0620/0621 and I
am able to ping my Win2K system from ThinkBlue and I can ping
ThinkBlue from Win2K(.ping 192.168.7.47 on Herc console).
2.95.3 2001
0319 (prerelease Red Hat Linux S/390)) #1 SMP Mon Oct 8 15:44:26 CEST
2001
My answers to ThinkBlue are as follows(and, yes, I saw the
FQDN - .linux390.company.com
Network device - .ctc0
IP address of VM - .192.168.7.244
IP address of ctc partner - .192.168.7.47
CTC device address - .auto
CTC driver Version: 1.49 initialized
ctc0: read: ch 0620 (irq 0017), write: ch 0621 (irq 0018) proto: 0
ctc0: connected with remote side
SIOCADDRT: No such device
ctc0 Link encap:Serial Line IP
inet addr:192.168.7.244 P-t-P:192.168.7.47
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MTU:32760 Metric:1
RX packets:86 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0
carrier:0

sarn756

2005-06-10 01:59:26 UTC

Permalink

One additional note. I came across an old reference to NIC cards
that had an offload checksum to CPU function. To ensure that this
was not my problem, when I got home this evening, I brought up Herc
w/ThinkBlue on my laptop with CTCI-W32. I then pinged it from my
desktop to ensure that it was working properly and ping sent/returned
all four packets. I then tried to telnet in with both the Win2K
command line and puTTY and both failed to connect. I am at a loss
here, folks. This configuration works perfectly under Linux and PING
functions properly under both. Telnet and FTP fail under Windows.

Post by sarn756
I never got a response on the problem below, but I would like to
throw in another bit of information. I brought up Herc 3.02 on a
Fedora Core 3 machine at home last night and was able to telnet into
the ThinkBlue installation with no problems using the same
configuration file(just different platform).
So the question still exists as to why I can ping the ThinkBlue Linux
across the CTC connection, but I cannot telnet to it using puTTY,
Reflections, or Windows command line telnet.

and

Post by sarn756
all was well. I am now attempting to install ThinkBlue Linux for
z/Series 7.1a.
I get to the point in the install, where it says to telnet into
the machine to continue the install and I hit a brick wall. I have
tried telnet from a cmd shell, I have tried it from Reflections,

and

Post by sarn756
I have tried it from puTTY with no luck. Any help here would be
greatly appreciated.
0620-0621 3088 CTCI -n 00-0D-56-E0-C2-EE 192.168.7.244

0.0.0.0

Post by sarn756
TunTap32.dll version 2.0.3.379 initiated
HHCCT073I 0620: TUN device tun0 opened
ThinkBlue is able to activate the CTC0 adapter at 0620/0621

and

Post by sarn756
I

Post by sarn756
am able to ping my Win2K system from ThinkBlue and I can ping
ThinkBlue from Win2K(.ping 192.168.7.47 on Herc console).
2.95.3 2001
0319 (prerelease Red Hat Linux S/390)) #1 SMP Mon Oct 8 15:44:26

CEST

Post by sarn756
2001
My answers to ThinkBlue are as follows(and, yes, I saw the
FQDN - .linux390.company.com
Network device - .ctc0
IP address of VM - .192.168.7.244
IP address of ctc partner - .192.168.7.47
CTC device address - .auto
CTC driver Version: 1.49 initialized
ctc0: read: ch 0620 (irq 0017), write: ch 0621 (irq 0018) proto: 0
ctc0: connected with remote side
SIOCADDRT: No such device
ctc0 Link encap:Serial Line IP
inet addr:192.168.7.244 P-t-P:192.168.7.47
Mask:255.255.255.255
UP POINTOPOINT RUNNING NOARP MTU:32760 Metric:1
RX packets:86 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:0 overruns:0
carrier:0

sarn756

2005-06-15 17:19:33 UTC

Permalink

This continues to get stranger every time I look at it.

I loaded up an operating system under Hercules that has its own IP
stack and is very easy to manipulate the IP parameters. I can telnet
from the guest OS to our company mainframe. I can telnet into the
guest OS from the company mainframe. One of my co-workers can telnet
into the guest OS from another location. However, I cannot Telnet
into the quest OS from the same Windows computer.

Can anyone explain why CTCI-W32 would behave this way?

and

Post by sarn756
I have tried it from puTTY with no luck. Any help here would be
greatly appreciated.
0620-0621 3088 CTCI -n 00-0D-56-E0-C2-EE 192.168.7.244

0.0.0.0

Post by sarn756
TunTap32.dll version 2.0.3.379 initiated
HHCCT073I 0620: TUN device tun0 opened
ThinkBlue is able to activate the CTC0 adapter at 0620/0621

and

Post by sarn756
I

CEST

Fish

2005-06-15 23:28:19 UTC

Permalink

Post by sarn756
This continues to get stranger every time I look at it.
I loaded up an operating system under Hercules that has its
own IP stack and is very easy to manipulate the IP parameters.
I can telnet from the guest OS to our company mainframe. I
can telnet into the guest OS from the company mainframe. One
of my co-workers can telnet into the guest OS from another
location. However, I cannot Telnet into the quest OS from the
same Windows computer.
Can anyone explain why CTCI-W32 would behave this way?

Routing? .. Firewall? ... Could be anything. <shrug>

Surf on over to:

http://www.softdevlabs.com/Hercules/ctci-w32-problem-reporting.html

and provide the requested information and maybe something will jump
out at me/us.

(No guarantees though; I'm kinda busy right now helping a paying
client, but maybe somebody else will see something to explain the
behavior you're experiencing)

- --
"Fish" (David B. Trout) - fish(at)infidels.org
Fight Spam! Join CAUCE! <http://www.cauce.org/>
(Any HTML email received will be deleted unread)

sarn756

2005-06-16 06:00:57 UTC

Permalink

Paying customers first, by all means!!!!!

I supplied the config information on my original post. I will sit
down and recreate all fo the other stuff asked for on your page in
the morning.

Thanks for taking the time to reply.

-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Routing? .. Firewall? ... Could be anything. <shrug>
http://www.softdevlabs.com/Hercules/ctci-w32-problem-reporting.html
and provide the requested information and maybe something will jump
out at me/us.
(No guarantees though; I'm kinda busy right now helping a paying
client, but maybe somebody else will see something to explain the
behavior you're experiencing)
- --
"Fish" (David B. Trout) - fish(at)infidels.org
Fight Spam! Join CAUCE! <http://www.cauce.org/>
(Any HTML email received will be deleted unread)
-----BEGIN PGP SIGNATURE-----
Version: PGP 7.0.4
iQA/AwUBQrC5kkj11/TE7j4qEQI8HQCgngas6PkYByP5mzQuJEusA/HZg5AAoM4S
OHhgM0alQwLOinJS7Ipwih9x
=MwA0
-----END PGP SIGNATURE-----

sarn756

2005-06-23 21:09:11 UTC

Permalink

Folks,

Just a final note on this issue. This was an I/O error, after
all. I/O as in idiot operator. There were two problems.
When starting hercules under CYGWIN, I was not paying attention
to routing. My company laptop has a route after booting up that
would be generated something like this:

route add 192.168.7.0 mask 255.255.255.0 192.168.7.37

Once I deleted this route, I could telnet to the installation
kernel for ThnkBlue Linux from Windows (2000) on the same machine.
The second problem involved the ThinkBlue connection after the
installation of Linux. You cannot telnet into this Linux system.
You must SSH into it.
I now have ThinkBlue64 7.1a Linux for S/390 up and am in the
process of configuring it. Once that is done, I will port it over to
a z/890 LPAR and IPL it there.

Thanks guys.

Steve A.