CTC unsuccess pinging Gateway

View: New views

2 Messages — Rating Filter: Alert me

CTC unsuccess pinging Gateway

by Kayhan :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

Hi,
I am trying to build a CTC connection between ZVM and My PC under Hercules 3.06 and using WinPcap 4.0.2, I couln't ping the gateway from ZVM. I succesfully pinging from ZVM to my PC (192.168.15.4) but it is unsuccess to 192.168.15.1
Does anyone has clues?
Thanks,
Regards,
Kayhan Tanriverir

Hercules CTC definition is :
0E20 3088 CTCI -n 00-19-D2-8F-A4-6E 192.168.15.85 0.0.0.0
0E21 3088 CTCI -n 00-19-D2-8F-A4-6E 192.168.15.85 0.0.0.0
Microsoft Windows XP [Version 5.1.2600]
Ethernet adapter Wireless Network Connection:
        Connection-specific DNS Suffix . :
        Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG Network Connection
        Physical Address. . . . . . . . . : 00-19-D2-8F-A4-6E
        Dhcp Enabled. . . . . . . . . . . : Yes
        Autoconfiguration Enabled . . . . : Yes
        IP Address. . . . . . . . . . . . : 192.168.15.4
        Subnet Mask . . . . . . . . . . . : 255.255.255.0
        Default Gateway . . . . . . . . . : 192.168.15.1
        DHCP Server . . . . . . . . . . . : 192.168.15.1
        DNS Servers . . . . . . . . . . . : 192.168.15.1
        Lease Obtained. . . . . . . . . . : 03 Kasım 2009 Salı 13:08:34
        Lease Expires . . . . . . . . . . : 05 Kasım 2009 Perşembe 13:08:34
ZVM TCPIP Configuration is below:
DEVICE DEVŞ0E20 CTC 0E20
LINK ETH0 CTC 0 DEVŞ0E20 MTU 9216
; (End DEVICE and LINK statements)
; ----------------------------------------------------------------------

HOME
192.168.15.85 255.255.255.0 ETH0
; (End HOME Address information)
GATEWAY
; Network       Subnet          First           Link             MTU
; Address       Mask            Hop             Name             Size
; ------------- --------------- --------------- ---------------- -----
192.168.15.1    255.255.255.0   =               ETH0             9216
DEFAULTNET                      192.168.15.0    ETH0             9216
; (End GATEWAY Static Routing information)
; ----------------------------------------------------------------------
START DEVŞ0E20
; (End START statements)

ifconfig -a
ETH0     inet addr: 192.168.15.85 mask: 255.255.255.0
         UP BROADCAST MULTICAST MTU: 9216
         vdev: 0E20 rdev: 0E20 type: CTC portnumber: 0
         cpu: 0 forwarding: ENABLED
         RX bytes: 240 TX bytes: 240
Ready; T=0.71/0.84 11:39:27

ping 192.168.15.1
Ping Level 530: Pinging host 192.168.15.1.
                Enter ÖCP EXT to interrupt.
PING: Ping Ö1 timed out
Ready(00004); T=1.53/2.55 11:40:16

ping 192.168.15.4
Ping Level 530: Pinging host 192.168.15.4.
                Enter ÖCP EXT to interrupt.
PING: Ping Ö1 response took 0.029 seconds. Successes so far 1.
Ready; T=0.52/1.12 11:40:38




Iyi calismalar, Saygilar / Regards

Kayhan Tanriverir

RE: CTC unsuccess pinging Gateway

by fish-8 :: Rate this Message:

Reply to Author | View Threaded | Show Only this Message

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

Kayhan Tanriverir wrote:

> Hi,
> I am trying to build a CTC connection between ZVM and My PC
> under Hercules 3.06 and using WinPcap 4.0.2, I couln't ping
> the gateway from ZVM. I succesfully pinging from ZVM to my PC
> (192.168.15.4) but it is unsuccess to 192.168.15.1
^^^^^^^^^^^^
^^^^^^^^^^^^

> Does anyone has clues?
> Thanks,
> Regards,
> Kayhan Tanriverir
>
> Hercules CTC definition is :
> 0E20 3088 CTCI -n 00-19-D2-8F-A4-6E 192.168.15.85 0.0.0.0
> 0E21 3088 CTCI -n 00-19-D2-8F-A4-6E 192.168.15.85 0.0.0.0
^^^^
^^^^

> Microsoft Windows XP [Version 5.1.2600]
> Ethernet adapter Wireless Network Connection:
^^^^^^^^
^^^^^^^^

> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/Wireless 3945ABG
> Network Connection
> Physical Address. . . . . . . . . : 00-19-D2-8F-A4-6E
> Dhcp Enabled. . . . . . . . . . . : Yes
> Autoconfiguration Enabled . . . . : Yes
> IP Address. . . . . . . . . . . . : 192.168.15.4
> Subnet Mask . . . . . . . . . . . : 255.255.255.0
> Default Gateway . . . . . . . . . : 192.168.15.1
^^^^^^^^^^^^
^^^^^^^^^^^^

> DHCP Server . . . . . . . . . . . : 192.168.15.1
> DNS Servers . . . . . . . . . . . : 192.168.15.1
> Lease Obtained. . . . . . . . . . : 03 Kasım 2009 Salı 13:08:34
> Lease Expires . . . . . . . . . . : 05 Kasım 2009 Perşembe 13:08:34
> ZVM TCPIP Configuration is below:
> DEVICE DEVŞ0E20 CTC 0E20
> LINK ETH0 CTC 0 DEVŞ0E20 MTU 9216
^^^^ ^^^^
^^^^ ^^^^

> ; (End DEVICE and LINK statements)
> ; ----------------------------------------------------------------------
>
> HOME
> 192.168.15.85 255.255.255.0 ETH0
> ; (End HOME Address information)
> GATEWAY
> ; Network Subnet First Link MTU
> ; Address Mask Hop Name Size
> ; ------------- --------------- --------------- ---------------- -----
> 192.168.15.1 255.255.255.0 = ETH0 9216

^^^^
^^^^

> DEFAULTNET 192.168.15.0 ETH0 9216
^^^^^^^^^^^^ ^^^^
^^^^^^^^^^^^ ^^^^

> ; (End GATEWAY Static Routing information)
> ; ----------------------------------------------------------------------
> START DEVŞ0E20
> ; (End START statements)
>
> ifconfig -a
> ETH0 inet addr: 192.168.15.85 mask: 255.255.255.0
> UP BROADCAST MULTICAST MTU: 9216
^^^^
^^^^

> vdev: 0E20 rdev: 0E20 type: CTC portnumber: 0
> cpu: 0 forwarding: ENABLED
> RX bytes: 240 TX bytes: 240
> Ready; T=0.71/0.84 11:39:27
>
> ping 192.168.15.1
^^^^^^^^^^^^
^^^^^^^^^^^^

> Ping Level 530: Pinging host 192.168.15.1.
> Enter ÖCP EXT to interrupt.
> PING: Ping Ö1 timed out
> Ready(00004); T=1.53/2.55 11:40:16
>
> ping 192.168.15.4
> Ping Level 530: Pinging host 192.168.15.4.
> Enter ÖCP EXT to interrupt.
> PING: Ping Ö1 response took 0.029 seconds. Successes so far 1.
> Ready; T=0.52/1.12 11:40:38

Suggestions:

1. Specify the correct gateway IP address.

Your say your gateway is 192.168.15.1, Windows says your default gateway is 192.168.15.1, you ping 192.168.15.1, but yet it is defined in your ZVM TCPIP Configuration as 192.168.15.0.

2. Specify a valid MTU.

You defined an Ethernet link on CTC device 0E20 in your ZVM TCPIP Configuration but specified an MTU size that is invalid for Ethernet. The maximum packet size that Ethernet can handle is 1500 bytes. The recommended MTU size is 1492.

3. Upgrade your CTCI device statements to the new format.

Your CTCI device statement are using a format that was deprecated several versions ago and which may not be supported in the future. Specifying "3088" as the protocol is deprecated. A properly formed CTCI device statement looks as follows:

0E20-0E21 CTCI -n 00-19-D2-8F-A4-6E 192.168.15.85 0.0.0.0

4. Check your Windows Firewall settings.

You may need to either add an exception for Hercules or turn it off altogether.

5. Run a TT32Test to verify proper CTCI-W32 functionality, *especially* given that you are using a wireless adapter.

Not all wireless adapters (in fact very few) support Promiscuous Mode which is a requirement for Hercules networking to function properly on Windows.

Additionally, some manufacturer's device drivers do not properly report their Checksum Offloading capabilities due to improperly coded support for Microsoft's new NDIS 6.1 (Network Device Interface Specification). If your adapter happens to be one of them then you will need to disable *all* outbound (i.e. "Tx" or "Transmit") Checksum Offloading. Usually there are separate entries for IP, TCP and UDP for both Tx (transmit) and Rx (Receive) Checksum Offloading for both IPv4 and IPv6, for a grand total of 12 separate settings. Make sure you disable *ALL* the Tx (Transmit) for IPv4: IP, TCP *and* UDP. (IPv6 doesn't matter since Hercules doesn't support IPv6, and Rx (Receive) Checksum Offloading doesn't matter, only Tx (Transmit) Checksum Offloading does.)

Be sure to do a ping test in both directions (from host to tt32test and from tt32test to host) from both the Windows host Hercules is running on AS WELL AS from another system/workstation on your local network if possible. Once everything works okay with TT32Test then and ONLY then can you be reasonably confident things should work okay with Hercules (barring any guest TCPIP configuration screw-ups of course :).

That's all I can think of at the moment. Others may have other input/advice.

Hope that helps.

Good luck!

- --
"Fish" (David B. Trout) - fish@...
Fight Spam! Join CAUCE! <http://www.cauce.org/>
7 reasons why HTML email is a bad thing
http://www.georgedillon.com/web/html_email_is_evil.shtml
PGP key fingerprints:
DH/DSS: 9F9B BAB0 BA7F C458 1A89 FE26 48F5 D7F4 C4EE 3E2A
RSA: 6B37 7110 7201 9917 9B0D 99E3 55DB 5D58 FADE 4A52

-----BEGIN PGP SIGNATURE-----
Version: PGP Desktop 9.8.0 (Build 2158)
Charset: utf-8

wj8DBQFK8JBRSPXX9MTuPioRAhY4AJsEI9LqSYIIUi+btFWnHkqbSxEycgCgoGBt
tlUEQMLjsGEEcVsoE+EGMcA=
=6Cd7
-----END PGP SIGNATURE-----