<div>
That did seem to do the trick, thanks.
</div>


<div>
<div class="content wysiwyg-content">
I am working off of an SBS 2011 server. &nbsp;The server is on a 192.168.1.x subnet. &nbsp;During a critical issue I moved the server to another network to make it easier to test / troubleshoot. &nbsp;The test network has a subnet of 172.16.1.x. &nbsp;To add the second IP I went through the network applet. &nbsp;After my repairs were complete I moved the server back to the 192.168.1 subnet and everything seemed fine. &nbsp;I noticed it seemed to take an little long to 'find the internet' &nbsp;but once it did all was fine. &nbsp;And internal service worked ok.<br />
<br />
In further research i discovered the NIC is retaining the 172.16.1.x IP address. &nbsp;I have tried to manually remove it for the networking applet. &nbsp;I have tried to re-run the internet connection wizard and I have looked in the registry for the 172... IP. &nbsp;No luck.<br />
<br />
where could it be pulling this IP address up from?
</div>
</div>


I am working off of an SBS 2011 server.  The server is on a 192.168.1.x subnet.  During a critical issue I moved the server to another network to make it easier to test / troubleshoot.  The test network has a subnet of 172.16.1.x.  To add the second IP I went through the network applet.  After my repairs were complete I moved the server back to the 192.168.1 subnet and everything seemed fine.  I noticed it seemed to take an little long to 'find the internet'  but once it did all was fine.  And internal service worked ok.

In further research i discovered the NIC is retaining the 172.16.1.x IP address.  I have tried to manually remove it for the networking applet.  I have tried to re-run the internet connection wizard and I have looked in the registry for the 172... IP.  No luck.

where could it be pulling this IP address up from?

rouge IP address bound to a NIC

I am working off of an SBS 2011 server.  The server is on a 192.168.1.x subnet.  During a critical issue I moved the server to another network to make it easier to test / troubleshoot.  The test network has a subnet of 172.16.1.x.  To add the second IP I went through the network applet.  After my repairs were complete I moved the server back to the 192.168.1 subnet and everything seemed fine.  I noticed it seemed to take an little long to &#39;find the internet&#39;  but once it did all was fine.  And internal service worked ok.

In further research i discovered the NIC is retaining the 172.16.1.x IP address.  I have tried to manually remove it for the networking applet.  I have tried to re-run the internet connection wizard and I have looked in the registry for the 172... IP.  No luck.

where could it be pulling this IP address up from?

Small Business Server (SBS) is a line of server operating systems targeted at small businesses by bundling the operating system with a number of other Microsoft products that would normally need to be purchased or licensed separately. The most notable inclusions are Exchange, SQL Server, SharePoint and ISA/TMG (Microsoft's firewall and proxy server).

The Microsoft Legacy Operating System topic includes legacy versions of Microsoft operating systems prior to Windows 2000: All versions of MS-DOS and other versions developed for specific manufacturers and Windows 3/3.1, Windows 95 and Windows 98, plus any other Windows-related versions, and Windows Mobile.

Microsoft Legacy OS

Transmission Control Protocol/Internet Protocol (TCP/IP) is the set of networking protocols that define end-to-end connectivity specifying how data should be packeted, addressed, transmitted, routed and received at the destination. This functionality is organized into four abstraction layers which are used to sort all related protocols according to the scope of networking involved.