Hello,

This may relate to this thread but I doubt it, but anyway. One of our
clients has Windows 2003 server, with an ADLS router for Internet access and
a LAN of 6 clients.

Apparently, this morning a workman installed an electric meter at the
premises. The staff shutdown the server, i'm not sure if this was done
properly, but afterwards they lost Internet access and email access, even
though the server and router were back on.

SERVER has static IP of 192.168.0.2 (DHCP turned on)
ROUTER has static IP of 192.168.0.1 (DHCP turned off)

I rebooted the router, the server and PCs, and noticed that the network card
on the server was trying to acquire a network address even though it has a
static ip. Also, an error kept appearing saying ip address conflict. In
addition, the DNS service was unable to start. I tried enabling this in
services but it came up with error 1222 'could not start the dns server
service'. I rebooted equipment 3 times and exactly the same thing happened,
checking all dns settings on the server, dhcp settings on the server and
router, event log, you name it.

I rebooted all equipment again but this time unplugged the router. This time
everything was fine, the network card was not trying to acquire an ip
address, the dns service had started and there was no ip conflict.

I then plugged in the router and the ip conflict reappeared. I did an arp
command and checked the devices attacted to the router when logging into the
router and could not find any duplicate ip addresses.

When doing an arp command it did say dynamic for the router ip address of
192.168.0.1 even though it was set to static. The strange thing is, ip
addresses 192.168.0.1 to .10 are excluded from the ip address range on the
server.

I didn't dare reboot the server as Internet and emails came back on, but i'm
apprehensive about the same thing happening if the server is rebooted.

Anyway, 2 out of 3 client PCs were getting an ip address from 192.168.0.1
(which is the router) the other was getting an ip address from 192.168.0.2
(which is the server), this concerned me.

From my gatherings I assume the problem lies with the router, does anyone
agree?

Many thanks for all for your support,
Jeff

Is DHCP supposed to be running on both the router and the server? It sounds
like you may need to disable DHCP on the router.

--
Greg Lindsay [MSFT]

Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

"jeffuk123" <jeffuk123@discussions.microsoft.com> wrote in message
news:F3E7027F-A4FA-48C8-9292-F1D63DF94A66@microsoft.com...
> Hello,
>
> This may relate to this thread but I doubt it, but anyway. One of our
> clients has Windows 2003 server, with an ADLS router for Internet access
> and
> a LAN of 6 clients.
>
> Apparently, this morning a workman installed an electric meter at the
> premises. The staff shutdown the server, i'm not sure if this was done
> properly, but afterwards they lost Internet access and email access, even
> though the server and router were back on.
>
> SERVER has static IP of 192.168.0.2 (DHCP turned on)
> ROUTER has static IP of 192.168.0.1 (DHCP turned off)
>
> I rebooted the router, the server and PCs, and noticed that the network
> card
> on the server was trying to acquire a network address even though it has a
> static ip. Also, an error kept appearing saying ip address conflict. In
> addition, the DNS service was unable to start. I tried enabling this in
> services but it came up with error 1222 'could not start the dns server
> service'. I rebooted equipment 3 times and exactly the same thing
> happened,
> checking all dns settings on the server, dhcp settings on the server and
> router, event log, you name it.
>
> I rebooted all equipment again but this time unplugged the router. This
> time
> everything was fine, the network card was not trying to acquire an ip
> address, the dns service had started and there was no ip conflict.
>
> I then plugged in the router and the ip conflict reappeared. I did an arp
> command and checked the devices attacted to the router when logging into
> the
> router and could not find any duplicate ip addresses.
>
> When doing an arp command it did say dynamic for the router ip address of
> 192.168.0.1 even though it was set to static. The strange thing is, ip
> addresses 192.168.0.1 to .10 are excluded from the ip address range on the
> server.
>
> I didn't dare reboot the server as Internet and emails came back on, but
> i'm
> apprehensive about the same thing happening if the server is rebooted.
>
> Anyway, 2 out of 3 client PCs were getting an ip address from 192.168.0.1
> (which is the router) the other was getting an ip address from 192.168.0.2
> (which is the server), this concerned me.
>
> From my gatherings I assume the problem lies with the router, does anyone
> agree?
>
> Many thanks for all for your support,
> Jeff

Hi Greg

As stated previously the router does not have DHCP enabled but the server
does!!!

"Greg Lindsay [MSFT]" wrote:

> Is DHCP supposed to be running on both the router and the server? It sounds
> like you may need to disable DHCP on the router.
>
> --
> Greg Lindsay [MSFT]
>
> Disclaimer: This posting is provided "AS IS" with no warranties, and confers
> no rights.
>
> "jeffuk123" <jeffuk123@discussions.microsoft.com> wrote in message
> news:F3E7027F-A4FA-48C8-9292-F1D63DF94A66@microsoft.com...
> > Hello,
> >
> > This may relate to this thread but I doubt it, but anyway. One of our
> > clients has Windows 2003 server, with an ADLS router for Internet access
> > and
> > a LAN of 6 clients.
> >
> > Apparently, this morning a workman installed an electric meter at the
> > premises. The staff shutdown the server, i'm not sure if this was done
> > properly, but afterwards they lost Internet access and email access, even
> > though the server and router were back on.
> >
> > SERVER has static IP of 192.168.0.2 (DHCP turned on)
> > ROUTER has static IP of 192.168.0.1 (DHCP turned off)
> >
> > I rebooted the router, the server and PCs, and noticed that the network
> > card
> > on the server was trying to acquire a network address even though it has a
> > static ip. Also, an error kept appearing saying ip address conflict. In
> > addition, the DNS service was unable to start. I tried enabling this in
> > services but it came up with error 1222 'could not start the dns server
> > service'. I rebooted equipment 3 times and exactly the same thing
> > happened,
> > checking all dns settings on the server, dhcp settings on the server and
> > router, event log, you name it.
> >
> > I rebooted all equipment again but this time unplugged the router. This
> > time
> > everything was fine, the network card was not trying to acquire an ip
> > address, the dns service had started and there was no ip conflict.
> >
> > I then plugged in the router and the ip conflict reappeared. I did an arp
> > command and checked the devices attacted to the router when logging into
> > the
> > router and could not find any duplicate ip addresses.
> >
> > When doing an arp command it did say dynamic for the router ip address of
> > 192.168.0.1 even though it was set to static. The strange thing is, ip
> > addresses 192.168.0.1 to .10 are excluded from the ip address range on the
> > server.
> >
> > I didn't dare reboot the server as Internet and emails came back on, but
> > i'm
> > apprehensive about the same thing happening if the server is rebooted.
> >
> > Anyway, 2 out of 3 client PCs were getting an ip address from 192.168.0.1
> > (which is the router) the other was getting an ip address from 192.168.0.2
> > (which is the server), this concerned me.
> >
> > From my gatherings I assume the problem lies with the router, does anyone
> > agree?
> >
> > Many thanks for all for your support,
> > Jeff
>
>
>

Hi Jeff,

You said that some clients are getting IP addresses from the router IP
address, which makes me think that even though DHCP is supposed to be off,
it isn't. Have you checked the router logs for anything unusual? I agree
with you that this is likely to be the problem. I've seen routers do some
strange things, and they don't always perform exactly as configured.

--
Greg Lindsay [MSFT]

Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

"jeffuk123" <jeffuk123@discussions.microsoft.com> wrote in message
news:54E3B1AE-6B0E-48D3-94EB-DF2C229D9375@microsoft.com...
> Hi Greg
>
> As stated previously the router does not have DHCP enabled but the server
> does!!!
>
> "Greg Lindsay [MSFT]" wrote:
>
>> Is DHCP supposed to be running on both the router and the server? It
>> sounds
>> like you may need to disable DHCP on the router.
>>
>> --
>> Greg Lindsay [MSFT]
>>
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>>
>> "jeffuk123" <jeffuk123@discussions.microsoft.com> wrote in message
>> news:F3E7027F-A4FA-48C8-9292-F1D63DF94A66@microsoft.com...
>> > Hello,
>> >
>> > This may relate to this thread but I doubt it, but anyway. One of our
>> > clients has Windows 2003 server, with an ADLS router for Internet
>> > access
>> > and
>> > a LAN of 6 clients.
>> >
>> > Apparently, this morning a workman installed an electric meter at the
>> > premises. The staff shutdown the server, i'm not sure if this was done
>> > properly, but afterwards they lost Internet access and email access,
>> > even
>> > though the server and router were back on.
>> >
>> > SERVER has static IP of 192.168.0.2 (DHCP turned on)
>> > ROUTER has static IP of 192.168.0.1 (DHCP turned off)
>> >
>> > I rebooted the router, the server and PCs, and noticed that the network
>> > card
>> > on the server was trying to acquire a network address even though it
>> > has a
>> > static ip. Also, an error kept appearing saying ip address conflict. In
>> > addition, the DNS service was unable to start. I tried enabling this in
>> > services but it came up with error 1222 'could not start the dns server
>> > service'. I rebooted equipment 3 times and exactly the same thing
>> > happened,
>> > checking all dns settings on the server, dhcp settings on the server
>> > and
>> > router, event log, you name it.
>> >
>> > I rebooted all equipment again but this time unplugged the router. This
>> > time
>> > everything was fine, the network card was not trying to acquire an ip
>> > address, the dns service had started and there was no ip conflict.
>> >
>> > I then plugged in the router and the ip conflict reappeared. I did an
>> > arp
>> > command and checked the devices attacted to the router when logging
>> > into
>> > the
>> > router and could not find any duplicate ip addresses.
>> >
>> > When doing an arp command it did say dynamic for the router ip address
>> > of
>> > 192.168.0.1 even though it was set to static. The strange thing is, ip
>> > addresses 192.168.0.1 to .10 are excluded from the ip address range on
>> > the
>> > server.
>> >
>> > I didn't dare reboot the server as Internet and emails came back on,
>> > but
>> > i'm
>> > apprehensive about the same thing happening if the server is rebooted.
>> >
>> > Anyway, 2 out of 3 client PCs were getting an ip address from
>> > 192.168.0.1
>> > (which is the router) the other was getting an ip address from
>> > 192.168.0.2
>> > (which is the server), this concerned me.
>> >
>> > From my gatherings I assume the problem lies with the router, does
>> > anyone
>> > agree?
>> >
>> > Many thanks for all for your support,
>> > Jeff
>>
>>
>>

Here is something I just thought of that commonly happens. If the router's
running config was changed and not saved to startup config, then a reboot
will cause those changes to be lost. Perhaps the router was providing DHCP
in the past, but was turned off, and then the config change wasn't saved to
startup. This might be something to check.

--
Greg Lindsay [MSFT]

Disclaimer: This posting is provided "AS IS" with no warranties, and confers
no rights.

"jeffuk123" <jeffuk123@discussions.microsoft.com> wrote in message
news:54E3B1AE-6B0E-48D3-94EB-DF2C229D9375@microsoft.com...
> Hi Greg
>
> As stated previously the router does not have DHCP enabled but the server
> does!!!
>
> "Greg Lindsay [MSFT]" wrote:
>
>> Is DHCP supposed to be running on both the router and the server? It
>> sounds
>> like you may need to disable DHCP on the router.
>>
>> --
>> Greg Lindsay [MSFT]
>>
>> Disclaimer: This posting is provided "AS IS" with no warranties, and
>> confers
>> no rights.
>>
>> "jeffuk123" <jeffuk123@discussions.microsoft.com> wrote in message
>> news:F3E7027F-A4FA-48C8-9292-F1D63DF94A66@microsoft.com...
>> > Hello,
>> >
>> > This may relate to this thread but I doubt it, but anyway. One of our
>> > clients has Windows 2003 server, with an ADLS router for Internet
>> > access
>> > and
>> > a LAN of 6 clients.
>> >
>> > Apparently, this morning a workman installed an electric meter at the
>> > premises. The staff shutdown the server, i'm not sure if this was done
>> > properly, but afterwards they lost Internet access and email access,
>> > even
>> > though the server and router were back on.
>> >
>> > SERVER has static IP of 192.168.0.2 (DHCP turned on)
>> > ROUTER has static IP of 192.168.0.1 (DHCP turned off)
>> >
>> > I rebooted the router, the server and PCs, and noticed that the network
>> > card
>> > on the server was trying to acquire a network address even though it
>> > has a
>> > static ip. Also, an error kept appearing saying ip address conflict. In
>> > addition, the DNS service was unable to start. I tried enabling this in
>> > services but it came up with error 1222 'could not start the dns server
>> > service'. I rebooted equipment 3 times and exactly the same thing
>> > happened,
>> > checking all dns settings on the server, dhcp settings on the server
>> > and
>> > router, event log, you name it.
>> >
>> > I rebooted all equipment again but this time unplugged the router. This
>> > time
>> > everything was fine, the network card was not trying to acquire an ip
>> > address, the dns service had started and there was no ip conflict.
>> >
>> > I then plugged in the router and the ip conflict reappeared. I did an
>> > arp
>> > command and checked the devices attacted to the router when logging
>> > into
>> > the
>> > router and could not find any duplicate ip addresses.
>> >
>> > When doing an arp command it did say dynamic for the router ip address
>> > of
>> > 192.168.0.1 even though it was set to static. The strange thing is, ip
>> > addresses 192.168.0.1 to .10 are excluded from the ip address range on
>> > the
>> > server.
>> >
>> > I didn't dare reboot the server as Internet and emails came back on,
>> > but
>> > i'm
>> > apprehensive about the same thing happening if the server is rebooted.
>> >
>> > Anyway, 2 out of 3 client PCs were getting an ip address from
>> > 192.168.0.1
>> > (which is the router) the other was getting an ip address from
>> > 192.168.0.2
>> > (which is the server), this concerned me.
>> >
>> > From my gatherings I assume the problem lies with the router, does
>> > anyone
>> > agree?
>> >
>> > Many thanks for all for your support,
>> > Jeff
>>
>>
>>