There was no reason for the the DC or anyother machine on the LAN to change IP#s
because the ISP was changed. You would probably solve many problems by just
putting the addresses back the way they were if you haven't already changed so
many other things that it would make it worse.
--
Phillip Windell [MCP, MVP, CCNA]
www.wandtv.com
The views expressed (as annoying as they are, and as stupid as they sound), are
my own and not those of my employer, or Microsoft, or anyone else associated
with me, including my cats.
-----------------------------------------------------
Understanding the ISA 2004 Access Rule Processing
http://www.isaserver.org/articles/IS...cessRules.html
Troubleshooting Client Authentication on Access Rules in ISA Server 2004
http://download.microsoft.com/downlo...7/ts_rules.doc
Microsoft Internet Security & Acceleration Server: Partners
http://www.microsoft.com/isaserver/partners/default.asp
Microsoft ISA Server Partners: Partner Hardware Solutions
http://www.microsoft.com/forefront/e...epartners.mspx
-----------------------------------------------------
<(E-Mail Removed)> wrote in message
news:(E-Mail Removed) ups.com...
> On Mar 30, 4:08 am, "Paul MaC" <paul.h...@thewebcompany.com.au> wrote:
>> Sounds like you have a second DHCP server running, maybe on a router.
>>
>> The next time it doesn't work type "ipconfig /all" at a command prompt. This
>> will show the DHCP servers ip address.
>>
>> Hope this helps to narrow things down.
>>
>> Regards,
>>
>> Paul MaC [MCSE]
>>
>> <craig....@gmail.com> wrote in message
>>
>> news:(E-Mail Removed) ups.com...
>>
>>
>>
>> > I'm somewhat of a newbie to networking and I've encountered an issue.
>>
>> > My company recently switched ISPs and as a result we have a new public
>> > IP address. During the whole ISP change the internal/private IP
>> > address for our DC got changed as well from 192.168.0.11 to
>> > 192.168.0.2.
>>
>> > Both DHCP and DNS services are running on this server (W2K). I've gone
>> > through the necessary steps and updated the NIC to reflect the new
>> > private IP address. I've also updated the DHCP Scope and Server
>> > Options to push the new private IP address for the DNS server.
>>
>> > Everything was fine for about a day, then random workstations in our
>> > network started receiving the OLD DNS server address of 192.168.0.11.
>> > As a result, they were not able to connect to the network or browse
>> > the Internet. As of right now the workaround that I have implemented
>> > is hard-code the DNS IP address in each computer's TCP/IP properties.
>>
>> > I've left my computer set to obtain DNS server address automatically,
>> > i.e. from the DHCP server. Every other day or so, my DNS server
>> > address will continues to revert to the old IP address, and I have to
>> > do an ipconfig release/renew to obtain the right DNS IP address. My
>> > DHCP server IP address is correct, so I'm confused as to why it
>> > sometimes sends out the wrong DNS IP address.
>>
>> > Any help would be greatly appreciated.- Hide quoted text -
>>
>> - Show quoted text -
>
>
> Thanks for the pointers Paul.
>
> I have tried ipconfig /all whenever my network connection fails,
> that's how I know that the DNS server is changed back to 192.168.0.11.
> It also shows my DHCP server IP address as 192.168.0.2, which is the
> correct address.
>
> I had a suspicion that there was another (rogue) DHCP server on our
> network, but I am unable to identify them if there are any. We have an
> AdTran router from our ISP. The physical hardware is the ISP's
> property and as such I don't have access to the configurations. I've
> spoken to various tech support reps and they informed me that DHCP is
> turned off on router.
>
> I've located the DHCP server logs, maybe there is something I should
> be looking for in there.
>
>
Similar Threads
Linear Mode
