Cannot add new computer to domain

[jer18]

Hey,

It seems my DHCP is failing, there have been a lot of strange things going on. For one, I cannot join a computer to a domain either wireless or wired. Also, for those on the domain, I cannot find printers in the directory. I restarted the servers and dhcp. Any help would be great. Thanks.

 

[jer18]

Mostly correct.

We have one DHCP server with a correct scope configured. "Any" computer connecting to the wired network will not automatically get an IP. I need to set a static of an unused IP available in the configured scope. Only then I can access internet, printers, network.

Not sure if this relates, but I have a wireless router to assign dhcp to wireless clients. They work fine in grabbing an IP and all over access to everything.

 

[TheCloak]

hey jer18 lets knock this out...

couple questions:
1. Can other computers connect to the server?
2. Can you ping the server by it's name? IP?
3. Have you restarted the computers on your network?
4. Have you powered off and back on your network gear?
5. Have you tried manually setting your IP and have the DNS pointing to the server?
6. Is windows firewall OFF (just for the time being) or any other firewall?


I have had many problems with this and a lot of the time it's because my DNS isn't pointing to the right place on the new computer. Could you try hooking it directly to a router or switch? Basically the computer is confused on itself and assigns a bogus ip. Are you sure the nic port your using is good?

Just covering the bases before we dig in.

--
-TheCloak

"You Never Know What Hits You, A Gunshot is the Perfect Way" - JFK

 

[jer18]

Sorry for the delayed response, thanks all for the continued support. Hopefully this is resolvable

1. Can other computers connect to the server?
Yes, only if configured with a static IP

2. Can you ping the server by it's name? IP?
Yes, only if configured with a static IP

3. Have you restarted the computers on your network?
Yes
4. Have you powered off and back on your network gear?
Yes
5. Have you tried manually setting your IP and have the DNS pointing to the server?
Yes, the only way it works.
6. Is windows firewall OFF (just for the time being) or any other firewall? Yes

 

[jer18]

Anyone think it is possible my severs can be on the wrong subnet on the nic settings? I believe before there was a problem one server was 255.255.255.0 and the other 255.0.0.0. Now they are identically 255.255.255.0 and I do not know which server had what setting..

 

[technome]

What AV software is installed ?


........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

 

[jer18]

Symantec, its always been there.

 

[pgaliardo]

I think you need to go back to Smokey's suggestion. You never verified that you tried his suggestion. Connect a workstation directly to your DHCP server with a cross-over cable. Try an ipconfig release and renew. If you still can't get an address, try another workstation. If the second one can't get an IP Address, you can be pretty sure that the problem lies with the server and you can eliminate that the problem lies in your switches or routers.

 

[technome]

Symantec, what version, with or without a firewall ?


........................................
Chernobyl disaster..a must see pictorial

http://www.kiddofspeed.com/default.htm

 

[jer18]

pgaliardo (MIS), I took a look at Smokey's post. I connected to the sever with a cross over cable into the laptop. Nothing happened. There were no link lights, and the computer was stating the network cable is unplugged

technome (IS/IT--Management), Symantec Corp. 8.1, I recently re-installed it to another drive to save on space. Not sure if this has any effect.

 

[DTracy]

Did you remember to set that laptop back to DHCP?

 

[jer18]

Yes, to obtain an ip address automatically.

 

[jer18]

Why when I connect directly to the server with a crossover, I get the 'network cable is unplugged' message...

 

[pgaliardo]

Sounds like a phsical problem with the cross over cable. Try this alternative. If you have a spare switch lying around, plug just the server and laptop into the switch and see what happens.

 

[jjjthird]

Have you factory rest the router?

 

[m1ckG]

Hi,

Have you checked:

1) The server has a static IP Set with correct Subnet.
2) You have activated the scope/and authorised the DHCP.
3) If you run NETDIAG on server from CMD prompt it might give you an indication of where the problem is. (Note: you need admin tools installed to run NETDIAG)

Apoligies if this has already been suggested had a quick look through the posts.

Regards
Mike


MCSA

 

[jer18]

Will attempt the above three posts later today, thanks!

 

[jer18]

Later today turned into later this month as things are getting busy at the office.

I ran a netdiag and the only thing that failed was:
DC List Test..... Failed to enumerate DCs by using the browser.

The static subnet on the server is 255.255.255.0 but on my laptop 255.0.0.0 and I am connected now with no prolem. I don't know which is correct to have at this point.

Did not get a chance to factory reset the router.

 

[JPJeffery]

I can't believe it's ever a good idea to have different subnet masks.

Still, that's not much help, you still have a very odd problem which I'm interested in the outcome of.

Have you considered setting up a new (physical) DHCP server?

JJ
[small][purple]Variables won't. Constants aren't[/purple]
There is no apostrophe in the plural of PC (or PST, or CPU, or HDD, or FDD, and so on)[/small]

 

[jer18]

Heh, replacing the server may be a solution, but I'd like to understand what Service Pack 2 would have changed...
Again, everything was working on SP1, server installs SP2 and reboots, no obtaining IP automatically..

I still have yet to:
1. Test server and a laptop on a spare switch
2. Hard reset on the netgear firewall/router