Failure to find domain controller (windows 95 on different subnet) 1

[Piloria]

We are trying to move between an old and a new IP address range so we have set up a gateway (windows 2000 machine 2 network cards) with nics in the old and the new networks.

in the old network we have the DHCP, DNS and domain controller.

in the new network the clients contact the dhcp server and get ip addresses in the new ip range

Windows 2000 clients work fine

windows 95 machines get all dhcp information but we get a message - unable to find domain controler. so cant log into the network.

 

[globalstrata]

Does Windows 95 machine have the Active Directory client installed? Did the Windows 95 PCs worked in the old network? Windows 95 will need either WINS or an LMhost. What I would do is create an LMHost file and copy it to all the machines via a batch file. The file should have the following:

Server <IP> #PRE #DOM:<Domain Name>

Gladys Rodriguez
GlobalStrata Solutions

http://www.globalstrata.com

 

[GlenJohnson]

Just throw in a hosts file at the root of windows. This is what I've done when I see connectivity problems. Have a valid copy of the hosts file on floppy and on network with documentation as to when I created it, and what revision level it's at. If I add a server, that info get's changed. If someone is having problems, I compare revision levels to make sure they are up to date. Good luck. Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us



&quot;Uniformity is death, diversity is life.&quot;
Mikhail A. Bakunin (1814-1876); Russian writer and revolutionary.

 

[globalstrata]

NOTE: Even though creating a host or a lmhost file may fix things, it increase the complexity of the network because if the IP address of the server ever changes, you have files pointing to different old IPs which creates a bunch of Name resolution problems. This is why, as soon as you do your whole migration, I would delete the host/lmhost files. This is why DNS and WINS were created. So you do not have to deal with this nightmate of uncentralized administration.

BTW, In an environment that has a lot of Windows 95/98/NT computers, I would also install a WINS Server. These operating systems use NETBIOS a lot and if you do not have a WINS, you get a lot of brocasts which, as you know, it will slow done the network.
Gladys Rodriguez
GlobalStrata Solutions

http://www.globalstrata.com

 

[koquito]

Did you check if the IP information on the Win95 computers is ok?
DNS particularly..
Try manually use one of those new IP addresses in your new range, will all the necesary information...restart it, and lets see what happens...IN case it works, then changed to use DHCP and restart it again. A+, MCP, CCNA
marbinpr@hotmail.com

Keep fighting for your knowledge!

 

[koquito]

Did you check if the IP information on the Win95 computers is ok?
DNS particularly..
Try manually use one of those new IP addresses in your new range, with all the necesary information...restart it, and lets see what happens...IN case it works, then changed to use DHCP and restart it again. A+, MCP, CCNA
marbinpr@hotmail.com

Keep fighting for your knowledge!

 

[bobbys9]

Have you tried a winipcfg/release and a winipcfg/renew? Also, are you sure the switch has not shut down the port the 95 machine is on? Try moving to a different switch on your new subnet.

 

[GlenJohnson]

Have a valid copy of the hosts file on floppy and on network with documentation as to when I created it, and what revision level it's at. If I add a server, that info get's changed. If someone is having problems, I compare revision levels to make sure they are up to date.

There are times when the simplest ways are best. You're talking w95 which doesn't have the best networking. I understand about IP's changing, that's why I keep revision levels on the host files. I'd still try a hosts file and see what happens. How's the ping? Ipconfig /all? Glen A. Johnson
Johnson Computer Consulting
MCP W2K
glen@johnsoncomputers.us



&quot;Uniformity is death, diversity is life.&quot;
Mikhail A. Bakunin (1814-1876); Russian writer and revolutionary.

 

[Piloria]

Thanks for the response
The propper message is

&quot;no domain server was available....&quot;

we tried the LMhosts file entry on a test machine and got the same message. we are trying to avoind this route as this will make admin so much harder as we are dealing with around 60 widly dispersed PC's

we have disabled netbios where we can so the wins server
isnt an option

i am finding references to &quot;Prefered master browser&quot; as a possible solution but i am lost as to what this is.

 

[Piloria]

After the system has booted and failed to access the domain controller
dns works
the machine has valid ip address fromdhcp
routing works fine

CANT see domain in network neighbourhood

 

[bobbys9]

If you have a valid ip address from the new dhcp and can't see the domain in network neighborhood, then you have a wins issue. The lmhost file would work. Are you sure you are not getting duplicate computer (netbios) names on the network? And are you sure that new dhcp is getting you to a wins server? Network neighborhood relies on the browser service. Might check that too.

 

[GiaBetiu]

Maybe a little late to give an answer but, these are some points to follow.
1. You have 2 networks! So, a broadcasting solution will not work without adjustments on router side.
2. How you router is performing? Standard IP communication I suppose that is working.
2. As I understand from you the DC is in one of the networks. The other network should be able to find it. For Win2k clients will not be a problem. For win9x then, the situation indeed is different because they will try to use NetBIOS resolution. Browser service is based on broadcasts.
3. Also, your other computers should have NetBIOS over TCP/IP activated.

Check NetBIOS name resolution. Choose one of the proposed strategy (WINS, LMHOST) and don't forget that you have a router there! Gia Betiu
m.betiu@chello.nl
Computer Eng. CNE 4, CNE 5, soon MCSE2k

 

[Piloria]

thanks for the help
we set up a wins server and it all works fine
(except our 2nd DHCP server put that is another post)