General discussion

Locked

NT4 DHCP client recieves no Gateway

By LordInfidel ·
I've been researching this issue for a while and have not been able to find any MS KB articles about it.

Basically, on my LAN, I have a mixed MS OS enviroment. I have several DHCP servers (NT4 srvr) handing out leases for a /25 block. All leases are for 24 hours and contain the generic IP/Mask/Gtwy/DNS.

The problem is most of My NT4 wkstn DHCP clients are not receiving the gateway as part of their lease. This has happened in the past and is generally more prevelant right after a IP Netwk address change.

After the last change over though it has become a daily occurence and is getting quite annoying.

2K and 98 clients have not issues receiving the full lease. The NT4 clients that experience this do not share any common switch. Some come in directlty into the noc to patch panel then into a switch. Others pass from switch to noc patch panel then into switch. We have multiple switches in the noc that connects the network together.

We are not using spanning tree on the switches.

Any ideas?

(originally I've changed out adapters thinking it was the adapter, I've re-run new drops.... I've stopped trying to fix it once I realized that the machines it was happening to were all NT4 wkstn's.)

This conversation is currently closed to new comments.

20 total posts (Page 2 of 2)   Prev   01 | 02
Thread display: Collapse - | Expand +

All Comments

Collapse -

NT4 DHCP client recieves no Gateway

by LordInfidel In reply to NT4 DHCP client recieves ...

Thx, I had already looked at that one. But it did not apply because all systems are local and the gtwy is a local address.

Collapse -

NT4 DHCP client recieves no Gateway

by haruss In reply to NT4 DHCP client recieves ...

I went bqack to a book that I have in my library, Since DHCP is a broadcast not all ruters (unless they are RFC-1542 compliant) will forward DHCP packets. The books solution was three fold. Install DHCP srever on each subnet. (too expensive) Install RFC-1542 routers, (also too expensive. Add a DHCP relay service on a WIN NT box on the subnet. May help. Also the book states that Windows NT uses DNS server addresses that is entered on the DNS page in Microsoft TCP/IP properties.

Why not add a default gateway to the workstations and not beat yor head on the ground? Just a suggestion..

Collapse -

NT4 DHCP client recieves no Gateway

by LordInfidel In reply to NT4 DHCP client recieves ...

All routers are rfc-1542 compliant, (we are a cisco shop). DHCP does not traverse the routers anyways.

The same wkstn can be plugged directly into the same switch that the dhcp srvr is on, and still not get the gtwy.

Your right, why not just assign a dflt gtwy to the wkstns. I did do that already.

It's just I have been living with this for the last couple of years. And I really dislike unsolved mysteries. Myself and 2 other admins at the company have looked at this and do not have an answer. Nor does anywone I ask.

I was hoping that someone, somewhere, has experienced the same behaviour that I am seeing.

Collapse -

NT4 DHCP client recieves no Gateway

Well, for NT Workstaions You might need to have WINS Servers, as well, to support Netbios names, .e.g

then, in a DHCP, You should describe WINS/NBNS Servers and WINS?NBT Node Types.

Thanks
David
P.S. Hope, it is not from another story ;-)

Collapse -

NT4 DHCP client recieves no Gateway

by LordInfidel In reply to NT4 DHCP client recieves ...

thanx for the comments david.

In this scenario, wins does not play a factor.

Wins helps in cutting down netbios name resolution broadcasts. But what I am talking about is the wkstn receiving and registering all dhcp options expect for the default gateway.

It does not make any sense and like I said before, it has remained a mystery on my network for the past few years and will probably remain until I get rid of the last DHCP enabled NT4 machine.

Collapse -

NT4 DHCP client recieves no Gateway

by paulo.sedrez In reply to NT4 DHCP client recieves ...

I read about something about NT4 DHCP server, I don't remember where: the server will only send the parameters requested by the client, not all parameters as other DHCP servers do.

So, check HKEY_LOCAL_MACHINE\Software\Microsoft\Tcpip for leftover gateway parameter (even all zeros).

Also (but I'm sure you checked this first) see that the default gateway is the 3 (ROUTER) DHCP parameter, and not 33 (GATEWAY or STATIC ROUTES). Just for sanity check.

--Sedrez

Collapse -

by LordInfidel In reply to NT4 DHCP client recieves ...

I appreciate the comments, but this question is dead.

This only occured in specific NT4 clients, regardless of the dhcp server they were being directed to. Meaning it was not global.

The netwk infrastructure has long been upgraded as well as all server's and wkstn's. This issue no longer exists and shall remain a mystery.

Collapse -

by kevin.stace In reply to NT4 DHCP client recieves ...

release and renew the NT4 wkst IP's with ipconfig /release and /renew, you will now notice that they have gateway connectivity.Your W2K & 98 wkst are unaffected as they have what is an inprovement on DHCP called "automatic client configuration" which automativaly renews the lease for the IP address given to the w2k or 98 clients when a connection is made with the DHCP server. A feature unavailable in DHCP client side with NT4 (hope this solves the mystery, still need to find a solution for NT4)

Collapse -

by LordInfidel In reply to

This was tried. But if it was true then this would be a more wide spread issue thru all networks (not just on mine) and the issue documented someplace. Basically it occured from only a few wkstn's (in a +1K user enviroment), and it did not matter which NT4 dhcp server it was getting the lease from.

Nor were they coming from the same vlan.

I appreciate the comments, but this question is dead, I apologize for not killing it earlier.

The netwk infrastructure has long been upgraded as well as all server's and wkstn's. This issue no longer exists and shall remain a mystery.

Collapse -

by LordInfidel In reply to NT4 DHCP client recieves ...

This question was closed by the author

Back to Windows Forum
20 total posts (Page 2 of 2)   Prev   01 | 02

Related Discussions

Related Forums