General discussion

Locked

DHCP & Domains

By Earthworm ·
Here is a tough one.

I run a network of 3 Servers (1 PDC, 1 BDC, 1 Member Server), and Approx. 50 Clients.
DHCP and WINS from PDC only. Clients are all Win98se or NT. A few 98 systems (4 to be exact) cannot use DHCP correctly. I want to know why.

Here is the info:

1 system a few months ago with DHCP enabled Would not Find the Domain. (The No domain available error) I found that the unit could not contact the DHCP server for some reason so I specified an IP in the subnet and all was A OK. So I ignored the problem.

Then a few months later a system I had just formatted and installed win98se onto had a similar but slightly different problem. This unit could see the DHCP server and get an IP address But the Login Screen wouldnot show a domain name. Thus logging in would login to windows but not the domain. So I specified an IP address and What do you know, everything showed up the next reboot. I was able to log into the domain, so again I ginored the issue and left that system outside the DHCP Server.

Now I have 2 new systems with the same problem as the last, but I have a little more Info just to confuse the situation.

1. If I log into windows (Without the domain name) and run winipcfg and release my IP address and then Renew it, A network login box apears with the domain listed.

2. I have tried 3 Different NIC's (a 3com, an Intel, and some noname NIC) All three same result.

3. The Computer actually registers itself with the WINS server, soPing works by IP or Name.

4. If I release the IP and reboot, the Network login box apears with Domain name, but after another reboot switches back to the Windows Login with no Domain.

5. Winipcfg looks identicle between systems that work andsystems that don't.

So what do you think? Any Help will be appreciated.

Eathworm

This conversation is currently closed to new comments.

55 total posts (Page 5 of 6)   Prev   03 | 04 | 05 | 06   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

DHCP & Domains

by Earthworm In reply to DHCP & Domains

This was the case when i took over, but I have been moving us in that direction ever since. As of december we are current on our licenses. Thanks anyway.

Collapse -

DHCP & Domains

by JackLR-UPS In reply to DHCP & Domains

Here's my small amount of experience 2-cents-worth. I know you don't think it is an issue with WINS, but just be sure, try setting it up with DHCP, but with static WINS addresses. I know that this is not a solution, but it may help you to troubleshoot.

Collapse -

DHCP & Domains

by Earthworm In reply to DHCP & Domains

WINS server is alread static in those systems due to DHCP problems. I have tested both ways and still get the same problem. Thanks anyway.

Collapse -

DHCP & Domains

by TheJazzMan In reply to DHCP & Domains

You mentioned in one of the info boxes that you have reserved the first 100 ip address's for fixed addresses and 100 through 255 for dhcp. 255 is a broadcast address. if dhcp is handing out that ip you will have problems with finding a domain serverjust for starters. Overall you will have a variety of eratic behavior on the machine that gets assigned that ip. Reset your dhcp address pool to not include any address ending with 0 or 255.

Collapse -

DHCP & Domains

by TheJazzMan In reply to DHCP & Domains

Also, after adjusting your dhcp address pool to not give out ip 255, remember to release all on the client before logging in with it to test. An obvious comment, but easily over looked in the heat of frustration

Collapse -

DHCP & Domains

by Earthworm In reply to DHCP & Domains

DHCP appears to be aware of this and has not handed that address out. 254 is the highest address assigned. Plus it will not allow me to use 192.168.1.254 for high end range, says it must be integrals of 32. Good thought though.

Collapse -

DHCP & Domains

by Earthworm In reply to DHCP & Domains

I figured it out. For those that are interested:

DHCP was configured incorrectly for the WINS server. In fact the only Scope Options set for DHCP was the Router option, and Domain Name. After correctly configuring the WINS Server, and NBT NodeType, I was able to remove the Hard coded Wins Server address on the Clients, and Use DHCP Correctly.

Thank you all for your responses. They were much appreciated.

Collapse -

DHCP & Domains

by Earthworm In reply to DHCP & Domains

Actually I guess colang@tiscalinet.it got it correct in the long list of things mentioned in that post, but I had already rejected it. So If colang@tiscalinet.it happens to read this message post a new answer and I will accept it. Sorry.

Other than that the question is closed.

Collapse -

DHCP & Domains

by rickh9 In reply to DHCP & Domains

Two more longshots:
1)Do any of these machines have DUN installed?
2)if your 10/100 hubs are office-connect hubs then I would expect odd behaviour. (although not like this) I would try inserting a basic 10t hub in the dhcp servers network path andplug the unit under test into that. (bypass the 3c hubs and switch.

Collapse -

DHCP & Domains

by Earthworm In reply to DHCP & Domains

Already Solved it. Check Comments

Back to Windows Forum
55 total posts (Page 5 of 6)   Prev   03 | 04 | 05 | 06   Next

Related Discussions

Related Forums