DHCP won't start....HELP!!

[Jeremy Eden]

So the event log shows the DHCP server encountered another server on the
network with IP address 192.168.1.1 belonging to the domain "." at 11 this
morning. I noticed because one person logged off and when they logged back
on, they had no internet. I have tried shutting all the computers on the
network down and rebooting the server and also tried restarting DHCP
multiple times. I keep getting the same error . Only one person was affected
before because nobody else logged off, but now they all logged off and
aren't getting internet. HELP!!! Suggestions? PLEASE??

The DHCP/BINL service on this computer running Windows Server 2003 for Small
Business Server has encountered another server on this network with IP
Address, 192.168.1.1, belonging to the domain: .

[David Copeland [MSFT]]

Jeremy,

Do you have a router on the network that has a DHCP server enabled? Or
maybe a machine enabled with ICS? Does the server have one nic or two? If
it has 2 then you may want to unplug them from the rest of the network to a
hub by itself and then start DHCP then check on the Properties of the
servername in the DHCP mmc/Advanced tab, Bindings button and ensure that the
DHCP server is only bound to your internal network card.

Otherwise, on the client getting the IP address from the 192.168.1.1 DHCP
server you should be able to ping 192.168.1.1 then do an arp -a to get the
MAC address of the nic to help track it down.

--

Hope that helps,
David Copeland
Microsoft Small Business Server Support

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

Newsgroups:
SBS v4.x : microsoft.public.backoffice.smallbiz
SBS 2000: microsoft.public.backoffice.smallbiz2000
SBS 2003: microsoft.public.windows.server.sbs

"Jeremy Eden" <je...@fulcrum-corp.com> wrote in message
news:esj1qfh...@tk2msftngp13.phx.gbl...

[Javier Gomez]

I hate to ask you this, but:
Do you have another DHCP server on your lan (perhaps a router and/or
firewall)?

If so, simply shutdown the service on the appliance.

BTW-> Are you using one NIC or two???

--
-Javier

<< SBS ROCK!!! >>

"Jeremy Eden" <je...@fulcrum-corp.com> wrote in message
news:esj1qfh...@tk2msftngp13.phx.gbl...

[Jfoster]

Did you have them disable and then enable their NIC cards
on their boxes to go and get a new IP address from the
DHCP server yet? Had a similar issue - had to DHCP
servers going - took one down. Went to each desktop -
depending on what OS they were running - right clicked on
the NIC - disabled - then enabled it... This made the NIC
go get a new lease for the IP address. Hope it helps for
you!.
J

>.
>

[Jeremy Eden]

Ok, so I think I have made some progress on the problem.....

1st, I was finally able to get the DHCP to restart properly by disconnecting
the server from the local network and rebooting. It worked fine for awhile,
but I still did not know what grabbed the address. About 3 hours later it
happened again. I tried pinging the address but it just timed out. On a
hunch I checked our linksys wireless router that is connected to the patch
panel and bingo! it is on 192.168.1.1

Now...to fix it. The router offers four setup types:

DHCP
Static
PPPoE
PPTP

No idea what the last two are, although it says the last one is Europe only.
I had it setup as DHCP and thought it would ask the server to assign it an
IP address and it would get a valid one. It has worked for months, but now
clearly this is not correct. Can someone give me some instruction on how I
should set it up?

Here are the options I have (not including encryption etc, because that all
has worked fine), as it reads on the setup menu for the wireless router:

Internet setup

Internet connection type: any of the above (currently at DHCP)
Host name: (currently blank)
Domain name: (currently blank)
MTU: (currently auto)

Network setup

Local IP address: (currently 192.168.1.1) --> assume this is the problem?
Subnet mask: (currently 255.255.255.0)

DHCP Server: (currently enable)---> doesn't this have to be enabled to dish
out IP's to the wireless workstations?
Starting IP address: (currently 192.168.1.100)
Max number of DHCP users: (currently 50)
Client lease time (currently 0) -->says that 0 means one day

Static DNS 1 --
Static DNS 2------these all read 0.0.0.0
Static DNS 3--
WINS--

Thanks for your help.

"Jfoster" <anon...@discussions.microsoft.com> wrote in message
news:01e701c3da1a$5f3eec70$a601...@phx.gbl...

[Jeremy Eden]

Well, as a temporary or possibly permanent fix, I have kept all the settings
I listed below the same, but have changed the IP address to 192.168.1.6
instead of 192.168.1.1

At least this should keep it from conflicting with the DHCP service. I still
don't understand why the device has been operating for months without this
conflict.

"Jeremy Eden" <je...@fulcrum-corp.com> wrote in message

news:OlniCxq2...@TK2MSFTNGP12.phx.gbl...