Solved

dhcp/dns issues on sbs 2008 domain

Posted on 2009-05-06
11
592 Views
Last Modified: 2012-06-27
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?
0
Comment
Question by:xzay1967
  • 6
  • 4
11 Comments
 

Author Comment

by:xzay1967
ID: 24321934
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)
0
 
LVL 14

Expert Comment

by:MCSA2003
ID: 24321964
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.
0
 

Author Comment

by:xzay1967
ID: 24322037
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.
0
3 Use Cases for Connected Systems

Our Dev teams are like yours. They’re continually cranking out code for new features/bugs fixes, testing, deploying, testing some more, responding to production monitoring events and more. It’s complex. So, we thought you’d like to see what’s working for us.

 
LVL 14

Expert Comment

by:MCSA2003
ID: 24322158
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.
0
 

Author Comment

by:xzay1967
ID: 24322238
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.
0
 
LVL 14

Expert Comment

by:MCSA2003
ID: 24322268
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.
0
 
LVL 14

Accepted Solution

by:
MCSA2003 earned 500 total points
ID: 24322269
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.
0
 

Author Comment

by:xzay1967
ID: 24322466
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.
0
 

Author Comment

by:xzay1967
ID: 24322700
I figured out the issue; it was Symantec EndPoint that was causing the issue. I had to reconfigure the network threat protection.
0
 

Author Closing Comment

by:xzay1967
ID: 31578843
Even though zi solved the issue myself, I am still giving you the points for trying.
0
 

Expert Comment

by:OccIT
ID: 24701444
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
0

Featured Post

DevOps Toolchain Recommendations

Read this Gartner Research Note and discover how your IT organization can automate and optimize DevOps processes using a toolchain architecture.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

So, you're experiencing issues on your network and you've decided that you need to perform some tests to determine whether your cabling is good.  You're likely thinking that you may need to spend money which you probably don't have on hiring/purchas…
SSL is a very common protocol used these days when browsing the web.  The purpose is to provide security to communication, but how does it do it?  There are several pieces at work that have to be setup before SSL will even work and it requires both …
Viewers will learn how to properly install and use Secure Shell (SSH) to work on projects or homework remotely. Download Secure Shell: Follow basic installation instructions: Open Secure Shell and use "Quick Connect" to enter credentials includi…
After creating this article (http://www.experts-exchange.com/articles/23699/Setup-Mikrotik-routers-with-OSPF.html), I decided to make a video (no audio) to show you how to configure the routers and run some trace routes and pings between the 7 sites…

810 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question