• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 189
  • Last Modified:

2008 R2 AD and Windows 7 Pro Computer

I have 2 domain controllers both 2008 R2. One is the Primary and other the Secondary. The Primary Server hands out DHCP addresses  to all computers with Windows 7 Pro. Here's the problem:::: For that last 2 weeks periodically I have been having different users not able to access certain mapped drives or Internet. I checked out the IP address they are receiving and for some reason when running the IPCONFIG /ALL I see a Windows 7 Pro computer as the DHCP server. Most of the time I can release and renew the IP address at that workstation and then it shows the correct dhcp server and then all functions work properly. I removed that Windows 7 Pro computer from domain that is showing as the dhcp server and even staticed the ip address and it still delegates out. does anyone have any clue why? I verified all the network settings on that Windows 7 Pro computer and it is configured like all the other workstations?
0
donebert
Asked:
donebert
  • 8
  • 3
2 Solutions
 
donebertAuthor Commented:
I also rebooted both Domain Controllers and it still has the issue
0
 
Schnell SolutionsSystems Infrastructure EngineerCommented:
Hello,

Could you confirm me that I understood correctly?

You took out the Windows 7 computer and the problem still persisted.



Additionally, Please be aware of the following things:

1. By default, Windows 7 does not assign IP addresses. Nevertheless, if you configure Internet Connection Sharing in this computer it could work as a DHCP server assigning 192.168.x.x addresses. Furthermore, the same is true if the computer has a third party software installed which assign address automatically

2. This is possible that a different system to your Windows 7 computer instance is the one assigning the IP addresses. It could include a communication device in your network or a virtual machine running from your Windows 7 computer
0
 
donebertAuthor Commented:
A windows 7 workstation IP Address on my network is showing up on a few other workstations as being the DHCP Server. I know this b/c I go to the workstation with network issues and run command ipconfig /all and instead of showing the DHCP Server as 100.100.100.248(PDC) it shows 100.100.100.65, which is the address of the windows 7 workstation. I attached the screen shot of the troubled computer.
DHCP.docx
0
Making Bulk Changes to Active Directory

Watch this video to see how easy it is to make mass changes to Active Directory from an external text file without using complicated scripts.

 
donebertAuthor Commented:
I have removed that workstation that is showing up as the DHCP Server from domain and re-joined it. However I used the same computer name. I will go ahead and remove that workstation from the domain and when I re-join I will give it a totally different name. Of course prior to re-joining to domain I will remove all references of that NetBIOS name in AD etc. I won't be able to do this until Monday.
0
 
Schnell SolutionsSystems Infrastructure EngineerCommented:
Good

Please test and let us know the results
0
 
MaheshArchitectCommented:
Please download Rogue DHCP server detection tool from below and try to find out on how many machines are acting as DHCP server in network
http://blogs.technet.com/b/teamdhcp/archive/2009/07/03/rogue-dhcp-server-detection.aspx

Then find why they are leasing DHCP addresses, based on screen shot i suspect that some software \ VMware \ is configured on multiple workstations and all those machines are acting as DHCP servers

You need to stop \ disable \ uninstall DHCP service on those machines in order to resolve the problem permanently

Mahesh
0
 
donebertAuthor Commented:
Thanks for that info Mahesh I will check it out and post results
0
 
Schnell SolutionsSystems Infrastructure EngineerCommented:
Have you found something?
0
 
donebertAuthor Commented:
Prior to removing from domain and rejoining.. I ran the Rogue DHCP tool and it did show the trouble windows 7 workstation, as well as our DC.  I verified all firewall settings/any different programs installed and network adapter setttings and saw nothing out of the ordinary on the workstation. I went ahead and removed CPU name from DNS and then Re-joined to our domain with a totally different computer name. The new computer name went into DNS properly and I re-ran the Rogue DHCP tool and it no longer finds it as a Rogue DHCP.

I will see how tommorow goes and re-post my results. I think it may be resolved. tommorow when everyone comes in and tries to connect I will no more.

thanks
0
 
donebertAuthor Commented:
OK, Things were fine until that user on that computer signed in. Now I am seeing the computer come up on the Rogue DHCP. So the issue came back. It appears to be something with her profile. I'm going to remove her temp files etc. and then see what happens I will post back tommorow with results
0
 
donebertAuthor Commented:
Ok, I went ahead and removed her local profile from the computer and re-created everything. I even gave it the original computer name and all is working. that Rogue DHCP was very helpful.

this has been resolved.
0
 
donebertAuthor Commented:
Thanks
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

  • 8
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now