Discussion:
CTCI-W32 challenge
(too old to reply)
dekel35
2006-06-24 15:09:54 UTC
Permalink
I Guess this one goes to fish:

Ever since I replaced my computer, no guest operating system is able
to use ctci-w32 on the new "Intel(R) PRO/1000 PM" adapter
(which is embeded on the 955xbk motherboard).
The only way to connect to a Hercules-hosted operating system is by
defining a loopback adapter, but even this would not
let me route anything past the physical computer on which Hercules
runs. i.e., even then the network
card blocks trafic comming from hercules through the loopback adapter.

(The guest operating system can ping itself (of course) and the PTP
addr, but nothing
beyond that)

I have tried everythig, including disabling the checksum offloading on
the card (there are 4 of them "tcp send", "tcp receive",
"ip send" and "ip receive"), but this did not help.

I have noted two things:
1. There is a CRC error on the card (DeviceIoControl(-2147483644)
failed; rc=23)
2. The loopback adapter apears to be disconnected (is this normal?)
but works OK

ipconfig /all output, followed by tt32test output:

Windows IP Configuration

Host Name . . . . . . . . . . . . : study-pc
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mynet

Ethernet adapter Loopback:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Loopback Adapter
Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.200.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : mynet
Description . . . . . . . . . . . : Intel(R) PRO/1000 PM
Network Conne
ion
Physical Address. . . . . . . . . : 00-13-20-AE-F6-A2
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 212.116.161.38
84.95.14.250
Lease Obtained. . . . . . . . . . : Saturday, June 24, 2006
4:56:18 PM
Lease Expires . . . . . . . . . . : Saturday, July 01, 2006
3:35:18 PM



17:50:59.390 ** CAdapter::SyncDeviceIoControl:
DeviceIoControl(-2147483644) failed; rc=23: Data error (cyclic
redundancy check).
17:50:59.390 ** CAdapter::FinishOpenAdapter:
QueryOID(OID_GEN_MEDIA_CONNECT_STATUS) failed; rc=23: Data error
(cyclic redundancy check).
17:50:59.390 Begin TT32Test.exe, version: "3.1.2.880" (3.1.2.880):
"Release version" ...
17:50:59.390 Copyright (C) 2002-2006, Software Development
Laboratories (aka 'Fish' (David B. Trout)).
17:50:59.390
17:50:59.390 Running on Windows XP (MP=2), version 5.1.2600 Service Pack 2
17:50:59.390
17:50:59.421 Using WinPCap Packet.dll, version "3, 1, 0, 27"
(3.1.0.27), driver version "3, 1, 0, 27" ...
17:50:59.421
17:50:59.421 Using FishPack.dll, version: "3.1.2.472" (3.1.2.472):
"Release version" ...
17:50:59.421 Copyright (C) 2002-2006, Software Development
Laboratories (aka 'Fish' (David B. Trout)).
17:50:59.421
17:50:59.421 Using TunTap32.dll, version: "3.1.2.846" (3.1.2.846):
"Release version" ...
17:50:59.421 Copyright (C) 2002-2006, Software Development
Laboratories (aka 'Fish' (David B. Trout)).
17:50:59.421
17:50:59.421 --------- The following relevant DosDevices are defined
---------
17:50:59.421
17:50:59.421 NPF_NdisWanBh
17:50:59.421 NPF_NdisWanIp
17:50:59.421 NPF_{06BA0941-945D-468E-8A67-9EDBE6ABFFA4}
17:50:59.421 NPF_{19258BF4-1837-47F4-923E-0C34176EA23C}
17:50:59.421 NPF_{1A5D849C-D7FA-4C67-B217-C7EA04780DDB}
17:50:59.421 NPF_{1A9C1B10-4436-4109-B62B-F2466F03AC90}
17:50:59.421 NPF_{4B7BA483-881F-4A75-A23B-0EAF3A2E61FE}
17:50:59.421 NPF_{54C7D140-09EF-11D1-B25A-F5FE627ED95E}
17:50:59.421 NPF_{5E8BD9D1-91BD-4292-883F-D02D684916B3}
17:50:59.421 NPF_{85D4B630-12B5-4160-B441-2B78DB295745}
17:50:59.421 NPF_{969AD90F-BF55-4254-9560-2A41F437781B}
17:50:59.421 NPF_{9E3A0606-CF7A-4DE7-B74C-87A25FBB2A14}
17:50:59.421 NPF_{A8ABA26D-BAF2-4A07-A569-263A766762AD}
17:50:59.421 {19258BF4-1837-47F4-923E-0C34176EA23C}
17:50:59.421 {1A5D849C-D7FA-4C67-B217-C7EA04780DDB}
17:50:59.421 {1A9C1B10-4436-4109-B62B-F2466F03AC90}
17:50:59.421 {85D4B630-12B5-4160-B441-2B78DB295745}
17:50:59.421 {969AD90F-BF55-4254-9560-2A41F437781B}
17:50:59.421 {9E3A0606-CF7A-4DE7-B74C-87A25FBB2A14}
17:50:59.421
17:50:59.421 ------------------------- Network Information
-------------------------
17:50:59.421
17:50:59.421 Host Name . . . . . . . . . : study-pc
17:50:59.421 Node Type . . . . . . . . . : (unknown)
17:50:59.421 DNS Servers . . . . . . . . : 212.116.161.38
17:50:59.421 84.95.14.250
17:50:59.421 IP Routing Enabled. . . . . : yes
17:50:59.421
17:50:59.421 Network Address Netmask Gateway Address
Interface Metric
17:50:59.421 0.0.0.0 0.0.0.0 192.168.2.1
192.168.2.3 20
17:50:59.421 127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1 1
17:50:59.421 192.168.2.0 255.255.255.0 192.168.2.3
192.168.2.3 20
17:50:59.421 192.168.2.3 255.255.255.255 127.0.0.1
127.0.0.1 20
17:50:59.421 192.168.2.255 255.255.255.255 192.168.2.3
192.168.2.3 20
17:50:59.421 192.168.200.0 255.255.255.0 192.168.200.2
192.168.200.2 30
17:50:59.421 192.168.200.2 255.255.255.255 127.0.0.1
127.0.0.1 30
17:50:59.421 192.168.200.255 255.255.255.255 192.168.200.2
192.168.200.2 30
17:50:59.421 224.0.0.0 240.0.0.0 192.168.2.3
192.168.2.3 20
17:50:59.421 224.0.0.0 240.0.0.0 192.168.200.2
192.168.200.2 30
17:50:59.421 255.255.255.255 255.255.255.255 192.168.2.3
192.168.2.3 1
17:50:59.421 255.255.255.255 255.255.255.255 192.168.200.2
192.168.200.2 1
17:50:59.421
17:50:59.421 Default gateway: 192.168.2.1
17:50:59.421
17:50:59.421 -------------------------- Detected Adapters
--------------------------
17:50:59.421
17:50:59.437 ** CAdapter::SyncDeviceIoControl:
DeviceIoControl(-2147483644) failed; rc=23: Data error (cyclic
redundancy check).
17:50:59.437 ** CAdapter::FinishOpenAdapter:
QueryOID(OID_GEN_MEDIA_CONNECT_STATUS) failed; rc=23: Data error
(cyclic redundancy check).
17:50:59.437 AdapterName =
NPF_{969AD90F-BF55-4254-9560-2A41F437781B}
17:50:59.437 Description = Intel(R) PRO/1000 PM Network Connection
17:50:59.437 PhysAddr = 00-13-20-AE-F6-A2
17:50:59.437 LinkType = NdisMedium802_3
17:50:59.437 MediaConnected = Yes
17:50:59.437 LinkSpeed = 100.0 Mbps
17:50:59.437 IPAddr = 192.168.2.3
17:50:59.437 IPAddrMask = 255.255.255.0
17:50:59.437 GatewayIPAddr = 192.168.2.1
17:50:59.437 dwIndex = 0x00050006
17:50:59.437 Checksum offloading = no
17:50:59.437
17:50:59.437 AdapterName =
NPF_{19258BF4-1837-47F4-923E-0C34176EA23C}
17:50:59.437 Description = Microsoft Loopback Adapter
17:50:59.437 PhysAddr = 02-00-4C-4F-4F-50
17:50:59.437 LinkType = NdisMedium802_3
17:50:59.437 MediaConnected = No ** CABLE
UNPLUGGED **
17:50:59.437 LinkSpeed = 10.0 Mbps
17:50:59.437 IPAddr = 192.168.200.2
17:50:59.437 IPAddrMask = 255.255.255.0
17:50:59.437 GatewayIPAddr = 0.0.0.0
17:50:59.437 dwIndex = 0x00000004
17:50:59.437 Checksum offloading = no
17:50:59.437
17:50:59.437 ** CAdapter::SyncDeviceIoControl:
DeviceIoControl(-2147483644) failed; rc=23: Data error (cyclic
redundancy check).
17:50:59.437 ** CAdapter::FinishOpenAdapter:
QueryOID(OID_GEN_MEDIA_CONNECT_STATUS) failed; rc=23: Data error
(cyclic redundancy check).





------------------------ Yahoo! Groups Sponsor --------------------~-->
Yahoo! Groups gets a make over. See the new email design.
http://us.click.yahoo.com/XISQkA/lOaOAA/yQLSAA/W4wwlB/TM
--------------------------------------------------------------------~->
Norman
2006-06-24 17:36:36 UTC
Permalink
I had similar types of challenges when I tried to get his all to work.

When I upgraded to Dell systems, the NIC was on the Motherboard.

One of my HERC buddies suggested that there may be things going on

under the covers on that NIC, and he found by adding another inexpensive

NIC card that he was able to make it all work. I also run a Web Server

and Photo Server. So I added a Linksys NIC just for HERC, and left the

other for the Web and Photo Server. It works fine, now. Please note, I

may have eventually got it all to work on 1 NIC; but $29 avoided a lot of

stress (and time that I had already put a lot into).



_____

From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org] On
Behalf Of dekel35
Sent: Saturday, June 24, 2006 SYSN 8:10 AM
To: hercules-390-***@public.gmane.org
Subject: [hercules-390] CTCI-W32 challenge



I Guess this one goes to fish:

Ever since I replaced my computer, no guest operating system is able
to use ctci-w32 on the new "Intel(R) PRO/1000 PM" adapter
(which is embeded on the 955xbk motherboard).
The only way to connect to a Hercules-hosted operating system is by
defining a loopback adapter, but even this would not
let me route anything past the physical computer on which Hercules
runs. i.e., even then the network
card blocks trafic comming from hercules through the loopback adapter.

(The guest operating system can ping itself (of course) and the PTP
addr, but nothing
beyond that)

I have tried everythig, including disabling the checksum offloading on
the card (there are 4 of them "tcp send", "tcp receive",
"ip send" and "ip receive"), but this did not help.

I have noted two things:
1. There is a CRC error on the card (DeviceIoControl(-2147483644)
failed; rc=23)
2. The loopback adapter apears to be disconnected (is this normal?)
but works OK

ipconfig /all output, followed by tt32test output:

Windows IP Configuration

Host Name . . . . . . . . . . . . : study-pc
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : mynet

Ethernet adapter Loopback:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Microsoft Loopback Adapter
Physical Address. . . . . . . . . : 02-00-4C-4F-4F-50
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.200.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . :

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . : mynet
Description . . . . . . . . . . . : Intel(R) PRO/1000 PM
Network Conne
ion
Physical Address. . . . . . . . . : 00-13-20-AE-F6-A2
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.2.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.2.1
DHCP Server . . . . . . . . . . . : 192.168.2.1
DNS Servers . . . . . . . . . . . : 212.116.161.38
84.95.14.250
Lease Obtained. . . . . . . . . . : Saturday, June 24, 2006
4:56:18 PM
Lease Expires . . . . . . . . . . : Saturday, July 01, 2006
3:35:18 PM

17:50:59.390 ** CAdapter::SyncDeviceIoControl:
DeviceIoControl(-2147483644) failed; rc=23: Data error (cyclic
redundancy check).
17:50:59.390 ** CAdapter::FinishOpenAdapter:
QueryOID(OID_GEN_MEDIA_CONNECT_STATUS) failed; rc=23: Data error
(cyclic redundancy check).
17:50:59.390 Begin TT32Test.exe, version: "3.1.2.880" (3.1.2.880):
"Release version" ...
17:50:59.390 Copyright (C) 2002-2006, Software Development
Laboratories (aka 'Fish' (David B. Trout)).
17:50:59.390
17:50:59.390 Running on Windows XP (MP=2), version 5.1.2600 Service Pack 2
17:50:59.390
17:50:59.421 Using WinPCap Packet.dll, version "3, 1, 0, 27"
(3.1.0.27), driver version "3, 1, 0, 27" ...
17:50:59.421
17:50:59.421 Using FishPack.dll, version: "3.1.2.472" (3.1.2.472):
"Release version" ...
17:50:59.421 Copyright (C) 2002-2006, Software Development
Laboratories (aka 'Fish' (David B. Trout)).
17:50:59.421
17:50:59.421 Using TunTap32.dll, version: "3.1.2.846" (3.1.2.846):
"Release version" ...
17:50:59.421 Copyright (C) 2002-2006, Software Development
Laboratories (aka 'Fish' (David B. Trout)).
17:50:59.421
17:50:59.421 --------- The following relevant DosDevices are defined
---------
17:50:59.421
17:50:59.421 NPF_NdisWanBh
17:50:59.421 NPF_NdisWanIp
17:50:59.421 NPF_{06BA0941-945D-468E-8A67-9EDBE6ABFFA4}
17:50:59.421 NPF_{19258BF4-1837-47F4-923E-0C34176EA23C}
17:50:59.421 NPF_{1A5D849C-D7FA-4C67-B217-C7EA04780DDB}
17:50:59.421 NPF_{1A9C1B10-4436-4109-B62B-F2466F03AC90}
17:50:59.421 NPF_{4B7BA483-881F-4A75-A23B-0EAF3A2E61FE}
17:50:59.421 NPF_{54C7D140-09EF-11D1-B25A-F5FE627ED95E}
17:50:59.421 NPF_{5E8BD9D1-91BD-4292-883F-D02D684916B3}
17:50:59.421 NPF_{85D4B630-12B5-4160-B441-2B78DB295745}
17:50:59.421 NPF_{969AD90F-BF55-4254-9560-2A41F437781B}
17:50:59.421 NPF_{9E3A0606-CF7A-4DE7-B74C-87A25FBB2A14}
17:50:59.421 NPF_{A8ABA26D-BAF2-4A07-A569-263A766762AD}
17:50:59.421 {19258BF4-1837-47F4-923E-0C34176EA23C}
17:50:59.421 {1A5D849C-D7FA-4C67-B217-C7EA04780DDB}
17:50:59.421 {1A9C1B10-4436-4109-B62B-F2466F03AC90}
17:50:59.421 {85D4B630-12B5-4160-B441-2B78DB295745}
17:50:59.421 {969AD90F-BF55-4254-9560-2A41F437781B}
17:50:59.421 {9E3A0606-CF7A-4DE7-B74C-87A25FBB2A14}
17:50:59.421
17:50:59.421 ------------------------- Network Information
-------------------------
17:50:59.421
17:50:59.421 Host Name . . . . . . . . . : study-pc
17:50:59.421 Node Type . . . . . . . . . : (unknown)
17:50:59.421 DNS Servers . . . . . . . . : 212.116.161.38
17:50:59.421 84.95.14.250
17:50:59.421 IP Routing Enabled. . . . . : yes
17:50:59.421
17:50:59.421 Network Address Netmask Gateway Address
Interface Metric
17:50:59.421 0.0.0.0 0.0.0.0 192.168.2.1
192.168.2.3 20
17:50:59.421 127.0.0.0 255.0.0.0 127.0.0.1
127.0.0.1 1
17:50:59.421 192.168.2.0 255.255.255.0 192.168.2.3
192.168.2.3 20
17:50:59.421 192.168.2.3 255.255.255.255 127.0.0.1
127.0.0.1 20
17:50:59.421 192.168.2.255 255.255.255.255 192.168.2.3
192.168.2.3 20
17:50:59.421 192.168.200.0 255.255.255.0 192.168.200.2
192.168.200.2 30
17:50:59.421 192.168.200.2 255.255.255.255 127.0.0.1
127.0.0.1 30
17:50:59.421 192.168.200.255 255.255.255.255 192.168.200.2
192.168.200.2 30
17:50:59.421 224.0.0.0 240.0.0.0 192.168.2.3
192.168.2.3 20
17:50:59.421 224.0.0.0 240.0.0.0 192.168.200.2
192.168.200.2 30
17:50:59.421 255.255.255.255 255.255.255.255 192.168.2.3
192.168.2.3 1
17:50:59.421 255.255.255.255 255.255.255.255 192.168.200.2
192.168.200.2 1
17:50:59.421
17:50:59.421 Default gateway: 192.168.2.1
17:50:59.421
17:50:59.421 -------------------------- Detected Adapters
--------------------------
17:50:59.421
17:50:59.437 ** CAdapter::SyncDeviceIoControl:
DeviceIoControl(-2147483644) failed; rc=23: Data error (cyclic
redundancy check).
17:50:59.437 ** CAdapter::FinishOpenAdapter:
QueryOID(OID_GEN_MEDIA_CONNECT_STATUS) failed; rc=23: Data error
(cyclic redundancy check).
17:50:59.437 AdapterName =
NPF_{969AD90F-BF55-4254-9560-2A41F437781B}
17:50:59.437 Description = Intel(R) PRO/1000 PM Network Connection
17:50:59.437 PhysAddr = 00-13-20-AE-F6-A2
17:50:59.437 LinkType = NdisMedium802_3
17:50:59.437 MediaConnected = Yes
17:50:59.437 LinkSpeed = 100.0 Mbps
17:50:59.437 IPAddr = 192.168.2.3
17:50:59.437 IPAddrMask = 255.255.255.0
17:50:59.437 GatewayIPAddr = 192.168.2.1
17:50:59.437 dwIndex = 0x00050006
17:50:59.437 Checksum offloading = no
17:50:59.437
17:50:59.437 AdapterName =
NPF_{19258BF4-1837-47F4-923E-0C34176EA23C}
17:50:59.437 Description = Microsoft Loopback Adapter
17:50:59.437 PhysAddr = 02-00-4C-4F-4F-50
17:50:59.437 LinkType = NdisMedium802_3
17:50:59.437 MediaConnected = No ** CABLE
UNPLUGGED **
17:50:59.437 LinkSpeed = 10.0 Mbps
17:50:59.437 IPAddr = 192.168.200.2
17:50:59.437 IPAddrMask = 255.255.255.0
17:50:59.437 GatewayIPAddr = 0.0.0.0
17:50:59.437 dwIndex = 0x00000004
17:50:59.437 Checksum offloading = no
17:50:59.437
17:50:59.437 ** CAdapter::SyncDeviceIoControl:
DeviceIoControl(-2147483644) failed; rc=23: Data error (cyclic
redundancy check).
17:50:59.437 ** CAdapter::FinishOpenAdapter:
QueryOID(OID_GEN_MEDIA_CONNECT_STATUS) failed; rc=23: Data error
(cyclic redundancy check).





[Non-text portions of this message have been removed]



------------------------ Yahoo! Groups Sponsor --------------------~-->
See what's inside the new Yahoo! Groups email.
http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/W4wwlB/TM
--------------------------------------------------------------------~->
dekel35
2006-06-24 18:43:07 UTC
Permalink
Yeah, I figured this would be the easiest solution at this stage. I
already tried upgrading the driver, tampering with the driver's
setting etc. to no avail.

BTW, Vmware is also unable to work with "bridged Networking" on this
card. I hope this is not a symptom for all these "new-generation"
cards which contain a lot of logic and functionality rather than just
passing the packets up and down...

Thanks for the input.
Dekel.
Post by Norman
I had similar types of challenges when I tried to get his all to work.
When I upgraded to Dell systems, the NIC was on the Motherboard.
One of my HERC buddies suggested that there may be things going on
------------------------ Yahoo! Groups Sponsor --------------------~-->
Yahoo! Groups gets a make over. See the new email design.
http://us.click.yahoo.com/XISQkA/lOaOAA/yQLSAA/W4wwlB/TM
--------------------------------------------------------------------~->
Norman
2006-06-24 19:43:51 UTC
Permalink
I think that is exactly the problem. I had the same problem with VMWare

and Linux under it. All went away when I added the 2nd card. I realize

that it should not happen; and no matter what I did to the driver, the

BIOS setup, configuring the card; it seemed to have a mind of its own.

So I let it, and got another one that didn't mind being configured. Not
that

it should matter, by I did get a Linksys, since my Router, Hub, and Access

Point are Linksys. I figured my hourly-rate for tinkering was far more than

the $29 investment.



_____

From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org] On
Behalf Of dekel35
Sent: Saturday, June 24, 2006 SYSN 11:43 AM
To: hercules-390-***@public.gmane.org
Subject: [hercules-390] Re: CTCI-W32 challenge



Yeah, I figured this would be the easiest solution at this stage. I
already tried upgrading the driver, tampering with the driver's
setting etc. to no avail.

BTW, Vmware is also unable to work with "bridged Networking" on this
card. I hope this is not a symptom for all these "new-generation"
cards which contain a lot of logic and functionality rather than just
passing the packets up and down...

Thanks for the input.
Dekel.
Post by Norman
I had similar types of challenges when I tried to get his all to work.
When I upgraded to Dell systems, the NIC was on the Motherboard.
One of my HERC buddies suggested that there may be things going on
[Non-text portions of this message have been removed]



------------------------ Yahoo! Groups Sponsor --------------------~-->
See what's inside the new Yahoo! Groups email.
http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/W4wwlB/TM
--------------------------------------------------------------------~->
Gary Brabiner
2006-06-25 01:54:38 UTC
Permalink
I second this …….

Same problem with the same relatively cheap solution, add an extra NIC card.



GaryB



-----Original Message-----
From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org] On
Behalf Of Norman
Sent: Sunday, 25 June 2006 05:44
To: hercules-390-***@public.gmane.org
Subject: RE: [hercules-390] Re: CTCI-W32 challenge



I think that is exactly the problem. I had the same problem with VMWare

and Linux under it. All went away when I added the 2nd card. I realize

that it should not happen; and no matter what I did to the driver, the

BIOS setup, configuring the card; it seemed to have a mind of its own.

So I let it, and got another one that didn't mind being configured. Not
that

it should matter, by I did get a Linksys, since my Router, Hub, and Access

Point are Linksys. I figured my hourly-rate for tinkering was far more than

the $29 investment.

_____

From: HYPERLINK
"mailto:hercules-390%40yahoogroups.com"hercules-390@-yahoogroups.-com
[mailto:HYPERLINK
"mailto:hercules-390%40yahoogroups.com"hercules-390@-yahoogroups.-com] On
Behalf Of dekel35
Sent: Saturday, June 24, 2006 SYSN 11:43 AM
To: HYPERLINK
"mailto:hercules-390%40yahoogroups.com"hercules-390@-yahoogroups.-com
Subject: [hercules-390] Re: CTCI-W32 challenge

Yeah, I figured this would be the easiest solution at this stage. I
already tried upgrading the driver, tampering with the driver's
setting etc. to no avail.

BTW, Vmware is also unable to work with "bridged Networking" on this
card. I hope this is not a symptom for all these "new-generation"
cards which contain a lot of logic and functionality rather than just
passing the packets up and down...

Thanks for the input.
Dekel.
Post by Norman
I had similar types of challenges when I tried to get his all to work.
When I upgraded to Dell systems, the NIC was on the Motherboard.
One of my HERC buddies suggested that there may be things going on
[Non-text portions of this message have been removed]




--
No virus found in this incoming message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.3/374 - Release Date: 23/06/2006
--
No virus found in this outgoing message.
Checked by AVG Free Edition.
Version: 7.1.394 / Virus Database: 268.9.3/374 - Release Date: 23/06/2006



[Non-text portions of this message have been removed]



------------------------ Yahoo! Groups Sponsor --------------------~-->
Great things are happening at Yahoo! Groups. See the new email design.
http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/W4wwlB/TM
--------------------------------------------------------------------~->
Fish
2006-06-25 14:33:41 UTC
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Norman wrote:

[..]
Post by Norman
I figured my hourly-rate for tinkering was far more
than the $29 investment.
Yup. If you just can't get it to work after a few minutes/hours of
tinkering (which should include checking to make sure you have all
the latest drivers for not only the card itself but also for the
MOTHERBOARD CHIPSET too (as well as, possibly, your BIOS too), then
you can save yourself a lot of stress and aggravation by simply going
out and buying a REAL[1] network card instead.

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

[1] By "real" I mean one that isn't designed *specifically* for
Windows (like those absolutely *horrible* "WinModems"[2] of days
past). Look for one that supports Linux too (or really *any* *OTHER*
operating system in addition to Windows). That should guarantee that
the card is a TRUE networking card (i.e. contains all the required
networking circuitry on it) and not one that requires additional o/s
support before it'll work. (I personally prefer REAL hardware and not
this cheapo "half hardware half software" crap that cheapo systems
seem to come with these days.)

[2] http://en.wikipedia.org/wiki/Winmodem

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBRJ6ew0j11/TE7j4qEQKcRQCdHXO84iXPYxCIwES+5b2f0uZ6hJMAnjiU
PJQ6vtXwWSn32Fpu24JbHYwo
=ljfO
-----END PGP SIGNATURE-----




------------------------ Yahoo! Groups Sponsor --------------------~-->
Yahoo! Groups gets a make over. See the new email design.
http://us.click.yahoo.com/XISQkA/lOaOAA/yQLSAA/W4wwlB/TM
--------------------------------------------------------------------~->
dekel35
2006-06-25 16:20:46 UTC
Permalink
--- In hercules-390-***@public.gmane.org, "Fish" <***@...> wrote:
.....
Post by Fish
Yup. If you just can't get it to work after a few minutes/hours of
tinkering (which should include checking to make sure you have all
the latest drivers for not only the card itself but also for the
MOTHERBOARD CHIPSET too (as well as, possibly, your BIOS too), then
you can save yourself a lot of stress and aggravation by simply going
out and buying a REAL[1] network card instead.
Thanks, Fish. I did try upgrading everything (Bios, Card driver
specifically, etc.). I will use the other gentlemen's' suggestions.
Hercules is just to good to not fully exploit.

Thanks again,
Dekel.







------------------------ Yahoo! Groups Sponsor --------------------~-->
Check out the new improvements in Yahoo! Groups email.
http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/W4wwlB/TM
--------------------------------------------------------------------~->
Norman
2006-06-25 19:28:25 UTC
Permalink
You can be sure that I have my BIOS current, the drivers updated, the

XP current. It just seems the NIC onboard want to have a mind of its

own. I don't have a loopback defined; but I can now get to Telnet, FTP,

and getting to HERC outside of my local network works great.



Protect your brain cycles, get the external NIC!



_____

From: hercules-390-***@public.gmane.org [mailto:hercules-390-***@public.gmane.org] On
Behalf Of dekel35
Sent: Sunday, June 25, 2006 SYSN 9:21 AM
To: hercules-390-***@public.gmane.org
Subject: [hercules-390] Re: CTCI-W32 challenge



--- In hercules-390@ <mailto:hercules-390%40yahoogroups.com>
yahoogroups.com, "Fish" <***@...> wrote:
.....
Post by Fish
Yup. If you just can't get it to work after a few minutes/hours of
tinkering (which should include checking to make sure you have all
the latest drivers for not only the card itself but also for the
MOTHERBOARD CHIPSET too (as well as, possibly, your BIOS too), then
you can save yourself a lot of stress and aggravation by simply going
out and buying a REAL[1] network card instead.
Thanks, Fish. I did try upgrading everything (Bios, Card driver
specifically, etc.). I will use the other gentlemen's' suggestions.
Hercules is just to good to not fully exploit.

Thanks again,
Dekel.





[Non-text portions of this message have been removed]



------------------------ Yahoo! Groups Sponsor --------------------~-->
Check out the new improvements in Yahoo! Groups email.
http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/W4wwlB/TM
--------------------------------------------------------------------~->
dekel35
2006-06-25 20:04:54 UTC
Permalink
Post by Norman
Protect your brain cycles, get the external NIC!
... I've just got one for exactly $29 (it's a 3com 3c905c, seemed the
most standard one and following Fish's recommendation, it has Linux
support [well, sort off, unofficial])






------------------------ Yahoo! Groups Sponsor --------------------~-->
Check out the new improvements in Yahoo! Groups email.
http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/W4wwlB/TM
--------------------------------------------------------------------~->
Fish
2006-06-25 14:18:17 UTC
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

dekel35 wrote:

[..]
Post by dekel35
BTW, Vmware is also unable to work with "bridged Networking"
on this card.
Well there you go! If OTHER software is ALSO having problems with the
card then chances are good it's the card itself that's at fault
(which includes its associated device drivers was well) and not the
software (e.g. WinPCap, CTCI-W32, Vmware, etc).

<snip>

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

iQA/AwUBRJ6bKEj11/TE7j4qEQLTXgCg8Ci1murmTLJGlab2I/wHuddBPWsAn2+z
dhyusuRpbxh1YvFEdgVTsFF9
=BHWb
-----END PGP SIGNATURE-----




------------------------ Yahoo! Groups Sponsor --------------------~-->
Great things are happening at Yahoo! Groups. See the new email design.
http://us.click.yahoo.com/TISQkA/hOaOAA/yQLSAA/W4wwlB/TM
--------------------------------------------------------------------~->
Fish
2006-06-25 14:14:06 UTC
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

Norman wrote:

[..]
Please note, I may have eventually got it all to work
on 1 NIC; but $29 avoided a lot of stress (and time that
I had already put a lot into).
That's good advice.

If, after updating all your drivers and trying various configuration
settings you still can't get a network adapter working, then the next
logical step is to try a different adapter altogether.

Perhaps it's just me but I personally feel that while network
adapters built into a motherboard are indeed handy from a "tinkering
under the hood" point-of-view (since, because they're built into the
motherboard itself, they thus don't consume any slots), using a
"real" Network Interface Card seems more reliable and less
problematic to me. <shrug>

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

iQA/AwUBRJ6aLUj11/TE7j4qEQLTHwCgzTh/MrsvFsnZaYFNEWpNqx9AJhsAoIQy
G4ueu2FJO70dtmTWaBL6EaG7
=/xib
-----END PGP SIGNATURE-----




------------------------ Yahoo! Groups Sponsor --------------------~-->
Something is new at Yahoo! Groups. Check out the enhanced email design.
http://us.click.yahoo.com/SISQkA/gOaOAA/yQLSAA/W4wwlB/TM
--------------------------------------------------------------------~->
Fish
2006-06-25 13:59:44 UTC
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

"Challenge" eh? :)
Post by dekel35
Ever since I replaced my computer, no guest operating
system is able to use ctci-w32 on the new "Intel(R)
PRO/1000 PM" adapter (which is embeded on the 955xbk
motherboard).
Hmmm... Doing some quick Googling reveals others have had problems
with this particular card / chipset too. Have you tried updating your
BIOS and motherboard drivers in addition to the driver for the card
itself? If not, then that'd be my first suggestion since it looks
like there have been some updates to them recently:

http://tinyurl.com/okrse
http://tinyurl.com/msg3c
Post by dekel35
The only way to connect to a Hercules-hosted operating
system is by defining a loopback adapter,
...(because of the Intel PRO/1000 PM adapter problem).
Post by dekel35
but even this would not let me route anything past the
physical computer on which Hercules runs.
Duh. :)
Post by dekel35
i.e., even then the network card blocks trafic comming from
hercules through the loopback adapter.
Eh?!
Post by dekel35
(The guest operating system can ping itself (of course) and
the PTP addr, but nothing beyond that)
Duh. :)

If you're using a Loopback adapter you're traffic is not going to go
any further than the system it's on. Your Windows host should be able
to ping Herc and vice versa (i.e. Herc s/b able to ping the loopback
adapter), but anything *beyond* that ain't gonna work (since, as you
claim, your REAL NIC isn't working).

Why does this surprise you? :)
Post by dekel35
I have tried everythig, including disabling the checksum
offloading on the card (there are 4 of them "tcp send",
"tcp receive", "ip send" and "ip receive"), but this did
not help.
Checksum Offloading SHOULDN'T be an issue any longer, as/of CTCI-W32
v3.1.0. Your problem lies elsewhere. (My guess is with the NIC
itself.)
Post by dekel35
1. There is a CRC error on the card
(DeviceIoControl(-2147483644) failed; rc=23)
That's "normal" for the MS Loopback Adapter due to a bug in
Microsoft's driver.[1] Until they fix it you're *always* going to see
that as long as you have their Loopback adapter installed. That's the
error that occurs as a result of their missing support for
OID_GEN_MEDIA_CONNECT_STATUS.
Post by dekel35
2. The loopback adapter apears to be disconnected
(is this normal?) but works OK
This is indeed normal for loopback adapters since, because they're
"virtual" in nature (i.e. they only exist in software; there's no
real, physical network card that the driver can talk to (it's all
being done by "smoke and mirrors" so to speak (much like CTCI-W32
itself!)))), no network cable can ever be plugged into it.
<snip report>


My only suggestions are to first try updating your BIOS and ALL of
your drivers -- starting with those for your motherboard (the chipset
drivers) and ending with the driver for your network card itself.

If that doesn't resolve your issue then review closely all of the
items mentioned in the F.A.Q:

http://www.softdevlabs.com/Hercules/ctci-w32-faq.html#wireless

paying particular attention to question #22 (the adapter binding
issue).

Lastly, as I see Norman has already suggested, when all else fails,
try using a different adapter. You can pick them up for pretty cheap
these days. (Doesn't need to be fancy/fast if all you're going to use
it for is Hercules networking.[2] <shrug>)


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

[1] The 'OID_GEN_MEDIA_CONNECT_STATUS' order id is, according to
THEIR OWN DOCUMENTATION(!), a *required* ("mandatory") order that ALL
network adapter drivers MUST support, but yet their own Loopback
Adapter driver fails it! Go figure. <shrug>

[2] This of course presumes your existing Intel PRO/1000 PM *does*
indeed otherwise work okay with your Windows system (i.e. I presume
you *can* use it to, say, access the internet and/or other
workstations on your LAN, etc?). If not (i.e. if the adapter is
indeed "dead" even from WINDOWS'S point-of-view), then you should of
course shop around for a good quality card and not a cheap one (and
then complain to the store where you bought your computer from too!
(and/or Intel themselves) You PAID for that built-in adapter after
all, so if it isn't working then you need contact the party/parties
responsible and demand they either fix it or refund your money.)

-----BEGIN PGP SIGNATURE-----
Version: PGP 8.1

iQA/AwUBRJ6Wzkj11/TE7j4qEQImfgCg2U8aSguC5w3mLkRnw4AtQsdN0jgAoKBS
8VDB5ZNwa1h77MAnEcgCjr1g
=7QxG
-----END PGP SIGNATURE-----




------------------------ Yahoo! Groups Sponsor --------------------~-->
Check out the new improvements in Yahoo! Groups email.
http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/W4wwlB/TM
--------------------------------------------------------------------~->
Fish
2006-06-25 16:05:30 UTC
Permalink
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1

[..]
If you're using a Loopback adapter you're traffic is ...
GAWD DAMN IT! <grumble> That's the *second* time today I ended up
using the wrong "your/you're". Sorry folks. I *do* know the
difference, I promise you. It's just seems my fingers don't today.

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

iQA/AwUBRJ60SUj11/TE7j4qEQLt8QCeI1gWGaTkeq7xz4b9IQ2tz15reFYAnjBB
tv3BtAZ8ZLEu3/N86VRpMv5K
=H1Sy
-----END PGP SIGNATURE-----




------------------------ Yahoo! Groups Sponsor --------------------~-->
Yahoo! Groups gets a make over. See the new email design.
http://us.click.yahoo.com/XISQkA/lOaOAA/yQLSAA/W4wwlB/TM
--------------------------------------------------------------------~->
Greg Smith
2006-06-25 18:46:00 UTC
Permalink
I here ya bro. Its definately annoying. Probally a sine of edutation
dese daze.
Post by Fish
[..]
If you're using a Loopback adapter you're traffic is ...
GAWD DAMN IT! <grumble> That's the *second* time today I ended up
using the wrong "your/you're". Sorry folks. I *do* know the
difference, I promise you. It's just seems my fingers don't today.
------------------------ Yahoo! Groups Sponsor --------------------~-->
Check out the new improvements in Yahoo! Groups email.
http://us.click.yahoo.com/6pRQfA/fOaOAA/yQLSAA/W4wwlB/TM
--------------------------------------------------------------------~->
Continue reading on narkive:
Loading...