Patrick,
Thanks for the reply, so to answer your questions:
- So "net initialize /dynamic" loads the e100b driver and correctly
identifies the network card?
Yes, it loads the e100b driver successfully and proceeds to netbind
and tcptsr. I also tried using the e100b drivers downloaded directly from
IBM and Intel. Neither has worked.
- Does this system have multiple NICs? If so, you might try disabling
one of them in the BIOS.
Yes, the system has two NICs. I have tried disabling them in the
BIOS, doing one then the other but still no luck. I will try it again to
make sure I didn't mess something up. But i'm pretty sure that failed too.
- Do things hang permanently, or do they eventually time out with an
error message? (If so, what message?)
Yes, they just hang. The line reads "Initializing TCP/IP via
DHCP..."
Here are the logged messages of the dhcp-attempt:
Jul 23 09:19:56 ent01 dhcpd: DHCPDISCOVER from 00:09:6b:58:2c:dc via eth1
Jul 23 09:19:56 ent01 dhcpd: DHCPOFFER on 172.30.1.177 to 00:09:6b:58:2c:dc
via eth1
Jul 23 09:19:56 ent01 dhcpd: Both dynamic and static leases present for
172.30.1.177.
Jul 23 09:19:56 ent01 dhcpd: Either remove host declaration feydpv07 or
remove 172.30.1.177
Jul 23 09:19:56 ent01 dhcpd: from the dynamic address pool for eth1
Jul 23 09:19:56 ent01 dhcpd: DHCPREQUEST for 172.30.1.177 from
00:09:6b:58:2c:dc via eth1
Jul 23 09:19:56 ent01 dhcpd: DHCPACK on 172.30.1.177 to 00:09:6b:58:2c:dc
via eth1
It looks to me like you could be correct that the IRQ is wrong and thus I am
not receiving messages. Is this something I can test easily, perhaps by
hardcoding an IRQ assignment in the BIOS to this NIC.
Some more info on the system that i forgot...
There are two NICs, one on the public network and one (the one
above) on a backend management network. Furthermore, these systems have two
extra "daisy-chain" ports, which are used to connect the x330s to each other
for console management, TFPT, power management, etc (very nifty).
Thanks again for the help,
Ed
-----Original Message-----
From: Patrick J. LoPresti [mailto:[EMAIL PROTECTED]
Sent: Tuesday, July 22, 2003 11:29 PM
To: Delgado, Ed
Cc: [EMAIL PROTECTED]
Subject: Re: [Unattended] RE: TCPTSR.EXE doesn't obtain address
"Delgado, Ed" <[EMAIL PROTECTED]> writes:
> The x330 family uses Intel Pro 100 NICs, using the E100B.dos driver.
>
> The network boot gets stuck when tcptsr.exe is called to get an
> address. Things just hang at this point.
So "net initialize /dynamic" loads the e100b driver and correctly
identifies the network card?
Does this system have multiple NICs? If so, you might try disabling
one of them in the BIOS.
Do things hang permanently, or do they eventually time out with an
error message? (If so, what message?)
Try "grep dhcpd /var/log/messages" on the DHCP server, and look for
entries with your machine's MAC address. I have seen DHCPREQUESTs
sent to the server and DHCPACKs sent back but never received by the
client. This is a symptom of the driver using the correct I/O address
but the wrong IRQ. The interrupt is only needed to receive packets,
not to send them... So if the IRQ is wrong, the driver can send DHCP
requests but cannot see the replies. (If this is the problem, we can
fix it with some hacks to protocol.ini.)
> I read somewhere on microsoft that tcptsr.exe would hang without
> options dhcp-rebinding-time and dhcp-renewal-time, which both have
> now been added to dhcpd.conf with a value of 300 (seconds). still
> no go.
I have never heard of this, nor do I set these options on my DHCP
server (RedHat Linux 6.2).
> Anyone have a similar type setup, or run into similar issues with
> tcptsr.exe? Is there anything I should specifically include in the
> dhcpd.conf file for the address to be returned? I really feel the
> issue is on the server end...
I would not be so sure. Definitely check the logs.
Can these machines boot from the network? If so, you might try that.
The "universal" undis3c.dos driver talks to the PXE stack, not the
network hardware. So at least it should fail differently :-).
- Pat
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info
-------------------------------------------------------
This SF.net email is sponsored by: VM Ware
With VMware you can run multiple operating systems on a single machine.
WITHOUT REBOOTING! Mix Linux / Windows / Novell virtual machines at the
same time. Free trial click here: http://www.vmware.com/wl/offer/345/0
_______________________________________________
unattended-info mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/unattended-info
