I have a Windows 7 desktop machine, having a static 192.168.*.* IP address on a network full of things with such addresses. I recently received a piece of hardware that I need that machine to talk to over UDP, and that piece of hardware has a built-in IP address of 10.*.*.*. So I went into my desktop's Internet Protocol Version 4 (TCP/IPv4) Properties
dialog, clicked Advanced
, and added a static 10.*.*.* address (on the same network card as my 192.168.*.* address, which is the only network card I have). That successfully allowed my desktop to talk to the new piece of hardware.
However, I later noticed that a backup script running on a different machine was no longer able to access my desktop. It tries to access my desktop as a network share, like \\desktopname\\foldername
. A little poking around revealed that that machine now considers "desktopname" to refer to the 10.*.*.* address that I set up, and it has no way to get to network, so it fails to get to my desktop.
That other machine is running Windows 2003 Server, and it does various things like DNS and DHCP for our network, and probably other Windows networking stuff that is essentially magic from my point of view (I'm just a programmer, not a sysadmin).
I assume that my desktop computer has announced that it is 10.*.*.*, either upon being asked by the server or just of its own volition.
I don't want any computer on the network to think that my desktop is 10.*.*.*. I want them all to keep thinking it's 192.168.*.*. The only reason I put added the 10.*.*.* address was to enable my computer to talk to that one particular piece of hardware; I don't want to have to go around to every computer on the network and give them all access to 10.*.*.*.
How can I get my computer to announce itself as 192.168.*.*, rather than 10.*.*.*? Or, if it announces both, to let other computers know that 192.168.*.* should be treated preferentially? I don't even know what "announce itself" really means. What sort of network discovery service or whatever might this be happening on?