Hello.

MyDHCP is giving out IP Address's corrently, which is great, how ever, i have 2 laptops on a test lab, when its plugged in to the network through ethernet it gets the IP of 192.168.1.189 and when it uses Wi-Fi it gets the ip of 192.168.1.13, Becuase it has the same computer name on both IPs i cannot apply GPO or any Remote Control, its still connecting to the Domain, and can still use the internet, and Terminal Server etc... so its reading the network fine... but is there a way for the Same IP of 192.168.1.189 to be given out to Both MAC Address's
Thanks

Hmm, I don't think so. If you did it would more than likely come back as a duplicate IP error. There may be a work around for this but if there is I don't know of it.

Even though both connection will not be enable at the same time, it will be Wired (if speed is needed) or wireless for flexibility.
If i manually set the Ip on Both Connections to the same IP, will the DHCP Server reject it?

Thanks for quick Reply

There should not be any issues with GPOs or Remote Control because it has a different IP Address, GPOs are deployed based on OUs and Objects with in them, the computer will be stored based on its SID, this should not change. Remote control should only be affected if you use IPs instead of Host names, It would be wiser to use hostnames as DHCP has expiry on addresses.

If you want both adapters to have the same IP specify a static IP for them both, and then reserve it in DHCP.

Note: One possible reason why Remote control might not work is firewall settings on the adapters not the same for both.

I've done what you suggested, all seems to work,but if i ping the Laptop from the server i dont get a response, only if i go back to Dynamic IP Address's does it recognise the laptop.

Again, Thanks for Help

DNS registration is probably not getting updated to reflect the new IP address. If you run "ipconfig /registerdns" on the laptop after switching connections, then watch the event logs on the server and client, make sure it updates properly (if not investigate the failures in the event log).

If you're using a Windows-based DHCP server, consider configuring the scope to always update A and PTR records when an IP address is given to a client (it does not do this by default unless the client requests it).