| Author |
Topic |
|
|
tom.hill
16 Posts |
 Posted - 30 Oct 2002 : 12:09:28
|
I have a Bitsy 3.17, Loader 1.75 with a Hawking CF686TX CF card.
When it first boots up, ipconfig shows 0.0.0.0 in the IpAddress and IpMask. After waiting for a few seconds, I do another ipconfig and I get a valid Dhcp-served address (i.e., 10.0.0.52) in the IpAddress. The mask is 255.255.255.0.
There is no value in the Gateway IpAddress and no value in the IpAddressList.
Any ping to this device times out.
Any ping from this device to a PC on the same subnet times out (11010).
Any ping beyond the subnet gives an unreachable error (11003).
Here is the NE20001 section from the ADSLOAD.REG I install:
[HKEY_LOCAL_MACHINE\Comm\NE20001\Parms\TcpIp]
"EnableDHCP"=dword:1
"IpAddress"="0.0.0.0"
"Subnetmask"="255.255.255.0"
"DefaultGateway"="10.0.0.254"
"DNS"="10.0.0.3"
"WINS"="10.0.0.3"
"DhcpServer"="10.0.0.3"
"DhcpSubnetMask"="255.255.255.0"
"AutoInterval"=dword:300
"AutoMask"="255.255.255.0"
"AutoSubnet"="10.0.0.0"
"DhcpWINS"="10.0.0.3"
"DhcpDNS"="10.0.0.3"
I've tried taking all of these out in turn and also all together. I've added other ones as well. This configuration has worked the best yet. Others won't even give me a valid dhcp-served address.
Any ideas?
|
|
|
tom.hill
16 Posts |
Posted - 30 Oct 2002 : 12:37:54
|
From the Bitsy I do a 'ping -t PCADDRESS'.
From my PC, I do a 'ping -t BITSYADDRESS'.
The Hawking RX light blinks at the same rate the PC is pinging the Bitsy.
The TX light blinks at the same rate the Bitsy is pinging the PC.
So it would appear the address is correct and I can, to some extent, get to it from the PC.
But both systems give me a 'Request timed out' or code 11010.
|
 |
|
|
akidder
1519 Posts |
Posted - 01 Nov 2002 : 18:19:58
|
| Hi Tom. You might try deleting all the unneeded entries. Comment out all but the "EnableDHCP"=dword:1 line and see what happens. I'm particularly leary of including those settings that begin with "DHCP".... |
|
|
|
tom.hill
16 Posts |
Posted - 04 Nov 2002 : 09:11:26
|
Actually, I started with just EnableDHCP=dword:1. But whenever it boots up it sets its IP address to 169.254.*.* (like, 169.254.7.96 or 169.254.238.107) with an IpMask of 255.255.0.0. I know there is no DHCP server on the line giving those addresses, since I get these same types of addresses when I disconnect the cable and restart.
Like I said, I have tried all kinds of combinations, from just EnableDHCP=dword:1 to all those I listed, plus others, minus others, etc. The list I gave got me the closest, in that when I ping from a workstation on the net I do see the Hawking RX lights blink in time with the pinging. But that's as far as it goes.
When connected like that, the pings from the Bitsy give 11010 as long as they are on the same subnet. Otherwise, I get 11003.
|
|
|
|
tom.hill
16 Posts |
Posted - 06 Nov 2002 : 17:11:25
|
We get the same results this way:
We connect two Bitsys, each with a Hawking CF686TX, to each other over with a crossover cable.
The .REG file for one has:
[HKEY_LOCAL_MACHINE\Comm\NE20001\Parms\TcpIp]
"EnableDHCP"=dword:0
"IpAddress"="192.168.10.10"
"Subnetmask"="255.255.255.0"
And the other has:
[HKEY_LOCAL_MACHINE\Comm\NE20001\Parms\TcpIp]
"EnableDHCP"=dword:0
"IpAddress"="192.168.10.11"
"Subnetmask"="255.255.255.0"
We have also tried adding these settings to both:
"LLInterface"=""
"UseZeroBroadcast"=dword:0
The results are the same every time. They both ping each other continuously:
ping -t 192.168.10.10 (or .11)
The result:
Pinging Host [192.168.10.10]
PING: transmit failed, error code 11010
The Link light is green.
The 100 light is orange.
The Full light is green.
The RX light blinks at the same rate as the ping on the other Bitsy.
The COL light never is lit.
The TX light blinks at the same rate as the ping on the Bitsy sending the ping. |
|
|
|
akidder
1519 Posts |
Posted - 08 Nov 2002 : 15:53:31
|
Hi Tom. Thanks for the additional details you provided. Here are a couple more things to try:
1. Look at your CE TCP/IP configuration
At the CE command prompt, type "ipconfig /all".
This will list the TCP/IP configuration of the active socket(s).
Does it match what you entered in the registry?
2. Test from PC
Preferrably, use an Ethernet switch or hub to connect the ADS board(s) to your PC. This eliminates the crossover cable as a potential source of the problem.
From the PC command prompt, PING the card from your PC. Then type "arp -a" on the PC.
The MAC address listed for the IP address you pinged should match the value listed on the underside of your Hawking card (12 hex digits).
|
|
|
|
tom.hill
16 Posts |
Posted - 08 Nov 2002 : 16:33:00
|
1. Yes, the ip info is correct. The only two items it displays are IpAddress and IpMask.
2. I switched back to connecting to a hub. Again, pinging from the PC turns on the Hawking RX light, but still times out without connecting. I've tried longer ping times, but to no avail. arp -a displays the MAC for the Bitsy as 00-00-00-00-00-00, type=invalid.
|
|
|
| |
Topic |
|
|
|
All Forums
Hardware
Timeout (11010) connecting to LAN
Forum Locked
Send Topic to a Friend
Printer Friendly