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 2 of 6)   Prev   01 | 02 | 03 | 04 | 05   Next
| Thread display: Collapse - | Expand +

All Comments

Collapse -

DHCP & Domains

by Earthworm In reply to DHCP & Domains

Nope Not really. I do get the login box, it just is not the right one. But i checked the reg settings and they were set correctly. And i'm not using policies.

Collapse -

DHCP & Domains

by jmason In reply to DHCP & Domains

Some of these will be silly but can you access any of the machines running win 98 from the PDC, (ping, net use, net send, vnc)or any other program you might have. Make sure no one has added any dial up settings. If they have and hard coated any winsor dns on the pc it will use those for resolution. Have you tried hard coating the wins and dns(if you use one) on the 98 machines. Have you tried reserving Ip addresses in DHCP. Also make sure you have this file for Windows sockets 2.0 Vdhcp.386 4.10.2012 06/22/98 01:12pm 56,175 bytes. Any mor einfo would be helpful.

Collapse -

DHCP & Domains

by Earthworm In reply to DHCP & Domains

Yes I can access these units from the Servers. The TCP/IP protocol and the NICs are working perfectly, the systems just won't ask for logging into a domain if They DHCP, but they do DHCP correctly as far as I can tell. Thanks anyway.

Collapse -

DHCP & Domains

by Frobo In reply to DHCP & Domains

Hi,

most Admins had the idea to have an second DHCP Server, for faulttolerance, with an deactivated scope. This is working fine just to the moment where SP4 for NT was released.

The second DHCP Server is now responding to the Clients even if it has no scope. The client gets no IP-Adress, because the secondary DHCP Server (the one with the deactivated Scope) is answering "no lease available". When the client starts a scond time, it functions very well and somtimes not !
This is a problem in SP4, Sp5, Sp6 and SP6a for NT 4.0. Deactivating the Scope is not enaugh, the service must be stopped on the secondary Server.

Collapse -

DHCP & Domains

by Earthworm In reply to DHCP & Domains

Checked both other servers, and neither are running another DHCP server. But like I said, the Clients do get DHCP addresses, and even register themselves with the WINS server. It is just the Network logon I am having problems with.

Collapse -

DHCP & Domains

by jpcorona In reply to DHCP & Domains

i think that you need to reinstall the network, please chek in the network properties that the client For microsoft Network is enabled, also in the Clinet for M n,put in the option windows NT domain, the correct domain.

are you using the tcp/ip?Because if you are using you need to check the option in the IP.
Obtain the IP addres Automaticaly
also check the option
Logon and restore network connection.

I using windows 95(Clients) and windows 2000 profesional (Client) and the windows Nt(server)

Good luck

Collapse -

DHCP & Domains

by Earthworm In reply to DHCP & Domains

Please See my question, All these solutions have already been tried.

Collapse -

DHCP & Domains

by Shanghai Sam In reply to DHCP & Domains

If you also have Novell client and IPX/SPX installed on the client, take them out.

Also, Control Panel --> Passwords --> All users use same setting should be unchecked. And the other setting should be checked.

In Control Panel --> System --> Access Control --> try User Level, instead of Share Level.

If none of them did it, try the following also.
1. Open "Regedit".
2. Go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Network
and
3. Add a new DWord value called DisablePwdCaching and set it to 1.
4. Reboot.

HTH.

Collapse -

DHCP & Domains

by Earthworm In reply to DHCP & Domains

Nope No Novell, No IPX. Access Rights should have no effect on Domain Login, but I tried it anyway, with no effect. PW Caching has already been disabled. Thanks anyway.

Collapse -

DHCP & Domains

by zk In reply to DHCP & Domains

If you also have Novell client and IPX/SPX installed on the client, take them out.

Also, Control Panel --> Passwords --> All users use same setting should be unchecked. And the other setting should be checked.

In Control Panel --> System --> Access Control --> try User Level, instead of Share Level.

If none of them did it, try the following also.
1. Open "Regedit".
2. Go to
HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Policies\Network
and
3. Add a new DWord value called DisablePwdCaching and set it to 1.
4. Reboot.

HTH.

Back to Windows Forum
55 total posts (Page 2 of 6)   Prev   01 | 02 | 03 | 04 | 05   Next

Related Discussions

Related Forums