Topic: DHCP not assigning IPs to local network

[Quade]

I installed v5.0 last night by performing a clean install over 4.1, which had been working properly. However, after a successful test for internet connection, my windows machine was unable to connect with my server to get an IP address.

I then forced the windows machine to use a static IP from my local network, but was still unable to see the Internet, as well as see the e-smith server.

DHCP is loading, and I've gone through all my config settings looking for something odd. The only thing I've noticed is that the local IP that e-smith wants to use is 192.168.34.x instead of 192.168.1.x which I am used to from the past.

Nothing else about the network has changed. It's got to be something simple I've overlooked. Any clues?

[Arkman]

Not sure this helps in the least, but I too experienced this after an upgrade. Went to static IP's and that seemed to fix things. Other people have experienced this as well:

http://forums.contribs.org/index.php?topic=11982.msg45029#msg45029

Arkman

[Quade]

Hmmm...interesting. So regardless of installation (fresh install or upgrade) random people have this problem.

Unfortunately, when I assign static IPs to the windows machine that can't connect using IP information for my local network, it still won't connect.

I've subsequently reinstalled v.5.0 twice and had the same problems. Tonight, I'll download the ISO again and make a new install CD and install from scratch.

Also, I noticed somehwere on this board that there's an alternate driver for an Intel NIC card. I'll try that driver, since my external NIC is an Intel 10/100 -- not the same card listed, but it's worth a shot. (even though the server can connect to the internet)

I wonder if the people in the other thread have the same NIC in their machines.

[Robert Boerner]

Before trying the NIC card option, I would do the following:

1) Use the log view option in the Server Manager to view all DHCP messages from /var/log/messages. DHCP is usually pretty verbose when it comes to problems, so you can try to see if it provides any insight.

2) Depending on what version of Windoze you are using, release all of the IP address leases. Sometimes, it refuses to let go of it's last IP address. On a Win9x machine, run winipcfg from the Run menu, and click on Release all. Shut down (don't reboot), and then see if it can get it's IP from the e-smith box.

I have had many issues support field travelers in my organization, and this is a very common problem.

Just my two cents tho, YMMV.

[Quade]

Thanks Robert. The second option worked like a charm. I like XP a lot, but I really, really hate that it tries to act smarter than me.