|
server
newsgroups
|
|||||||||||||||||||||||
|
|||||||||||||||||||||||
Issues Possibly From Joining a DomainThis is a puzzling situation. There are two networks. One network is not on any type of domain, a large workgroup that obtains DHCP leases from a proxy firewall that also provides Internet access (192.168... range). There is also a Win 2K3 network that has a domain and its own DHCP server in the 10... range. Both networks have Windows XP and Vista clients. Both networks are in different buildings. There are two clients from the workgroup that were joined to the Win2K3 network. After the clients joined the Win 2K3 network, the workgroup began to have workstations that indicate that there are duplicate IPs in the workgroup. I am going to make the following assumptions: 1 In this situation, in order for the workgroup workstations to be joined to the Win2K3 domain, they would have to have a static Win2K3 address, a valid DNS address, and have the ability to reach a DC (all 10...). 2 Because they are in different address ranges, they would have to have routing established to "talk" with one another. Based on this information, why would the workgroup start having duplicate IPs? Would joining the Win2K3 domain cause problems or interference with the workgroup? Would Active Directory itself be causing issues? -- Thank you for your help! JYC Hello Mr. JYC,
If you join a workstation from one physical network to another, that shouldn't have any influence of the previuos network. Also the DHCP server should not have problems with that. Or is that machine using multiple NIC's and you have configured just a second NIC to the other network? This shouldn't be domain problem, for networking you can also use this NG, i will crosspost this: microsoft.public.windows.server.networking Best regards Meinolf Weber Disclaimer: This posting is provided "AS IS" with no warranties, and confers no rights. ** Please do NOT email, only reply to Newsgroups ** HELP us help YOU!!! http://www.blakjak.demon.co.uk/mul_crss.htm Show quoteHide quote > Hello, > > This is a puzzling situation. > > There are two networks. One network is not on any type of domain, a > large workgroup that obtains DHCP leases from a proxy firewall that > also provides Internet access (192.168... range). There is also a Win > 2K3 network that has a domain and its own DHCP server in the 10... > range. Both networks have Windows XP and Vista clients. Both > networks are in different buildings. There are two clients from the > workgroup that were joined to the Win2K3 network. After the clients > joined the Win 2K3 network, the workgroup began to have workstations > that indicate that there are duplicate IPs in the workgroup. > > I am going to make the following assumptions: > > 1 In this situation, in order for the workgroup workstations to be > joined > to the Win2K3 domain, they would have to have a static Win2K3 address, > a > valid DNS address, and have the ability to reach a DC (all 10...). > 2 Because they are in different address ranges, they would have to > have > routing established to "talk" with one another. > Based on this information, why would the workgroup start having > duplicate IPs? > > Would joining the Win2K3 domain cause problems or interference with > the workgroup? Would Active Directory itself be causing issues? > Howdie!
Mr. JYC wrote: > 1 In this situation, in order for the workgroup workstations to be joined Correct.> to the Win2K3 domain, they would have to have a static Win2K3 address, a > valid DNS address, and have the ability to reach a DC (all 10...). > 2 Because they are in different address ranges, they would have to have > routing established to "talk" with one another. > Based on this information, why would the workgroup start having duplicate IPs? check whether the workstations have an "Alternate Configuration" assigned in their TCP/IP properties. That config gets applied if they can't contact a DHCP server. Cheers, Florian -- Microsoft MVP - Group Policy eMail: prename [at] frickelsoft [dot] net. blog: http://www.frickelsoft.net/blog. Maillist (german): http://frickelsoft.net/cms/index.php?page=mailingliste As others have said dhcp and AD are unrelated.
Go into the dhcp manager on both devices that provide leases and start looking for leases that are coming up as duplicate to try and track down which machine is causing you the issues. -- Show quoteHide quotePaul Bergson MVP - Directory Services MCTS, MCT, MCSE, MCSA, Security+, BS CSci 2008, 2003, 2000 (Early Achiever), NT4 http://www.pbbergs.com Please no e-mails, any questions should be posted in the NewsGroup This posting is provided "AS IS" with no warranties, and confers no rights. "Mr. JYC" <Mr***@discussions.microsoft.com> wrote in message news:919B6445-391E-46DE-8A5F-5393B14A5B82@microsoft.com... > Hello, > > This is a puzzling situation. > > There are two networks. One network is not on any type of domain, a large > workgroup that obtains DHCP leases from a proxy firewall that also > provides > Internet access (192.168... range). There is also a Win 2K3 network that > has > a domain and its own DHCP server in the 10... range. Both networks have > Windows XP and Vista clients. Both networks are in different buildings. > There are two clients from the workgroup that were joined to the Win2K3 > network. After the clients joined the Win 2K3 network, the workgroup > began > to have workstations that indicate that there are duplicate IPs in the > workgroup. > > I am going to make the following assumptions: > > 1 In this situation, in order for the workgroup workstations to be joined > to the Win2K3 domain, they would have to have a static Win2K3 address, a > valid DNS address, and have the ability to reach a DC (all 10...). > 2 Because they are in different address ranges, they would have to have > routing established to "talk" with one another. > > Based on this information, why would the workgroup start having duplicate > IPs? > > Would joining the Win2K3 domain cause problems or interference with the > workgroup? Would Active Directory itself be causing issues? > > -- > Thank you for your help! > JYC Thank you All!
-- Show quoteHide quoteThank you for your help! JYC "Mr. JYC" wrote: > Hello, > > This is a puzzling situation. > > There are two networks. One network is not on any type of domain, a large > workgroup that obtains DHCP leases from a proxy firewall that also provides > Internet access (192.168... range). There is also a Win 2K3 network that has > a domain and its own DHCP server in the 10... range. Both networks have > Windows XP and Vista clients. Both networks are in different buildings. > There are two clients from the workgroup that were joined to the Win2K3 > network. After the clients joined the Win 2K3 network, the workgroup began > to have workstations that indicate that there are duplicate IPs in the > workgroup. > > I am going to make the following assumptions: > > 1 In this situation, in order for the workgroup workstations to be joined > to the Win2K3 domain, they would have to have a static Win2K3 address, a > valid DNS address, and have the ability to reach a DC (all 10...). > 2 Because they are in different address ranges, they would have to have > routing established to "talk" with one another. > > Based on this information, why would the workgroup start having duplicate IPs? > > Would joining the Win2K3 domain cause problems or interference with the > workgroup? Would Active Directory itself be causing issues? > > -- > Thank you for your help! > JYC 
Other interesting topics
Error while trying to upgrade a Windows 2000 Server domain
BDC not serving logons when PDC goes down... Netlogon not working when one DC is down.. AD 2k8 SetPassword access denied Schema transfer error Determin the Class an Attribute Belongs To Justification for creating a new Domain Fault Tolerance in FSMO role Certificate Services 2008 |
|||||||||||||||||||||||
