asked on

dhcp/dns issues on sbs 2008 domain

I setup a sbs 2008 domain today. I have a 2wire in bridge mode connected to a netgear firewall. Internet works fine, the DC is giving out IPs like it should. Well I setup three work stations on the domain, but two keep getting limited or no connectivity errors on both of them. If I give them a static ip address they connect fine, and can ping the server. The other computer gets ip addresses fine from the server with no issue. what am i missing?

xzay1967

ASKER

Update: To try to isolate the issue, I moved the computer that connected fine to the port one of the problem comouters is conected to; it connected fine. That leads me to believe that the issue is not with the server, but with the workstations. These are two new HP computers (dont' know if that helps)

MCSA2003

go to network properties and make sure it is selected for "obtain ip address automatically". Go to start > run >cmd enter and type in ipconfig /all . What is the ipaddress it is pulling? Is it in your ip range? Also make sure gateway is correct.

xzay1967

ASKER

The issue is not with the static ip setting. When I assign IP manually, it works fine. Even though I can get to the internet, and ping the sever fine when it has a static IP, I still cannot go to http://connect so it can join the domain. If I set to receive an IP automatically, I get a limited connectivity error. I connect a laptop to the port where the troubled desktop is having issues, and the laptop get assigned an IP automatically with no problem. So, I wonder what is wrong with these two desktops.

MCSA2003

Im confused. You say that when you statically assign the clients with an ip address everything works fine? If this is the case, there is an issue with the DHCP scope/server. It almost sounds like you do not have the gateway address listed under the DHCP scope. Set the NIC on the client to DHCP, and do the command I said in my other post and post the results.

xzay1967

ASKER

I understand what you are saying, but the other computer does not have a static IP, and it works fine. But, I will do as you asked. when I use the cmd ipconfig /all, I get 169.254.211.47 for the ip address. I know that means it is not reaching the dhcp server. If I do ipconfig /renew, I get cannot reach dhcp server, timedout. This is very odd, the other computer gets its IP just fine from the server, not sure why these two desktop won't. I even edit the host file, still no luck.

MCSA2003

Right click on my computer and go to properties. Select device manager. Are there any yellow exclamation showing? Could be that the drivers are not installed for the nics.

ASKER CERTIFIED SOLUTION

MCSA2003

membership

This solution is only available to members.

To access this solution, you must be a member of Experts Exchange.

Start Free Trial

xzay1967

ASKER

That does not make sense. If the drivers for the nic cards were not installed, then they would not show up in the system tray, nor would I be able to assign static ip addresses to them. The computer I am typing this message from is has a static ip address. If it was set to dynamically get an ip, it would fail, and the limited connectivity error would display. Don't get me wrong, I appreciate you trying to help, but it really a mystery why one computer is able to get ip's from the server, when the others can't.

xzay1967

ASKER

I figured out the issue; it was Symantec EndPoint that was causing the issue. I had to reconfigure the network threat protection.

xzay1967

ASKER

Even though zi solved the issue myself, I am still giving you the points for trying.

OccIT

What did you change on Endpoint? I am experiencing the same issue. I tried to add a DHCP rule to the default policy but it is still not working properly.

Thanks