Re: DHCP not working right after server restore from backup

Problem fixed! Thanks to all who listened to me rant and plea for
assistance!

The whole problem seemed to be linked to old information in both DHCP and
DNS.

A while back, when we switched ISP's I reconfigured the scope of dhcp but
the old information was still listed in the console. So I killed it. Didnt
help. But from your message (the part about the DNS) I got the bright idea
to check out that console, and I found that same old info (the old scope) in
there also. I held my breath, deleted the old, restarted, and BINGO, up and
running!!!

Thanks guys!! I will finally let this thread die. I definitely need a
drink, I'm buying if anyone wants......

"Jim Behning SBS MVP" <jimbehning@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in
message news:k2bst4tfjhf4q75r15lplb44jqo8f0788q@xxxxxxxxxx
Workstation and server are supposed to have the server's ip entered.
The Internet has no knowledge of your private domain, Active Directory
and workstations. That is why you enter your SBS ip for dns.

Make sure you do not test from just one workstation. Try it from a
good laptop or other workstation. DHCP should be working as should
dns. I take my laptop out of my car. If I do not get proper ip stuff
from the server then I know thew network is goofed up.

If you have something messed up on your SBS then it may not answer a
ping. What might be messed up is hard to say. From one workstation to
another they should be able to ping each other by ip. If you set up
dns properly it should be able to answer ping by name.

Can the server ping the workstations?

Have you rebooted your network switch or switches?

Have you moved the SBS from one port on the network switch to another
port? Ports do get stuck or go bad on occasion.

On Thu, 9 Apr 2009 12:03:26 -0400, "M. Murphy"
<MMurphy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:

Another restore, still having dhcp strangeness,
following your input, but the CEICW won't start when there is no scope, so
I
followed this article
http://support.microsoft.com/kb/875422
CEICW ran fine, set the scope, again all looks good in DHCP land, BUT same
problem with workstations.
went to a workstation, entered a static ip, from the excluded range, set
the
dns to the isp's dns server.
From that setup, I can ping the router (.168) and can't ping the server
using either its name, or its ip address. Restarted router and firewall
just to be sure they are not messing with me, and still no good.

How can restoring from a backup be so difficult?


"Les Connor [SBS MVP]" <les.connor@xxxxxxxxxxxx> wrote in message
news:uYmxzQHuJHA.1212@xxxxxxxxxxxxxxxxxxxxxxx
Delete the Scope from DHCP, and stop the DHCP service.
Go to c:\windows\system32\dhcp and rename dhcp.mdb to some other name.
Start DHCP service, and then run the CEICW.
See that the scope is re-created.

from a workstation, restart, or do ipconfig /renew and see if it will
pick
up an IP.

--
-----------------------------------------------
Les Connor [SBS MVP]

"M. Murphy" <MMurphy@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:efotEF7tJHA.4488@xxxxxxxxxxxxxxxxxxxxxxx
Hi,
I restored my server from a backup, following the instructions found
here:
http://www.microsoft.com/smallbusiness/support/articles/backup_restore_sbs2003.mspx

Just about everything went very well, but I am now having problems with
DHCP, as in none of the workstations can contact the DHCP server.

Immeadiatly after the restore was done, I had to go into admin tools >
dhcp
right click the server> properties> advanced > credentials, and give
it
the proper information. I was getting event id 1056 after the restore
and found this:
http://support.microsoft.com/kb/282001 so I entered the info, and the
DHCP seemed to be working, at least on the server end with no errors.

Trouble is that none of the workstations will agree with my last
statement. I ran CIECW and still no good. I set a workstation with a
static ip and it won't ping the server or won't see the internet.

Some workstations were still on during the restore, and I can ping
those,
but any one that was off or restarted can not be pinged. I can ping
the
2 printers on the network (they have static ip).

ipconfig from server:
Windows IP Configuration
Host Name . . . . . . . . . . . . : cetek01
Primary Dns Suffix . . . . . . . : Cetek.local
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : Yes
WINS Proxy Enabled. . . . . . . . : Yes
DNS Suffix Search List. . . . . . : Cetek.local

Ethernet adapter Server Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Attansic L1 Gigabit Ethernet
10/100/1000Base-T Adapter
Physical Address. . . . . . . . . : 00-18-F3-64-97-56
DHCP Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 192.168.168.2
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.168.168
DNS Servers . . . . . . . . . . . : 192.168.168.2
Primary WINS Server . . . . . . . : 192.168.168.2

Ipconfig from workstation that has been restarted:


Windows IP Configuration
Host Name . . . . . . . . . . . . : reception
Primary Dns Suffix . . . . . . . : Cetek.local
Node Type . . . . . . . . . . . . : Broadcast
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Atheros L2 Fast Ethernet
10/100 Base-T Controller
Physical Address. . . . . . . . . : 00-22-15-78-EF-3D
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
Autoconfiguration IP Address. . . : 169.254.9.131
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

forgot to mention server is SBS 2003 R2 standard.
I need to git-r-done soon as nobody is getting any email at the moment!
THANKS!!!!



See what SBS support is working on
http://blogs.technet.com/sbs/default.aspx
Check your SBS with the SBS Best Practices Analyzer
http://blogs.technet.com/sbs/archive/tags/BPA/default.aspx


.

Relevant Pages

  • Re: DHCP IP lease renewal ok, but a new PC can not obtain an IP ("An e
    ... I guess the problem seen with DHCP from PC's is a symptom of another ... Note that both robert and tina are blade servers within the save blade ... Connection-specific DNS Suffix. ... I.e. DNS servers has their own IP as the first DNS server and another as ...
    (microsoft.public.windows.server.networking)
  • Re: Domain controllers
    ... other DNS was still on the zones transferred to the new domain controller. ... Both DHCP and WINS databases CAN be move -- there are KB ... from one server to another -- search Googgle against Microsoft ...
    (microsoft.public.win2000.active_directory)
  • Re: AD Newbie Questions
    ... Remember that though DNS and AD are ... You can copy the profile over, either doing a straight copy (get the ... > I've reviewed a few books on Server2K3, but before I> promote my server to a Domain Controller, there are still a few specifics> where I'd appreciate some guidance. ... I would install Studio.NET on the XP Pro workstation. ...
    (microsoft.public.windows.server.active_directory)
  • Re: where is the outlook 2003 product key on the SBS2003 R2 DVD
    ... tracking is easier from the server. ... All you need to do is make sure there are no other DHCP servers running on ... The only time I have seen the connectcomputer error you mentioned about DNS ... I couldn't get the client to ...
    (microsoft.public.windows.server.sbs)
  • Re: Basic Active Directory Questions
    ... Primary DC DNS service was disabled. ... Seondary DNS server has problem address with this DC ... Point your Member server and workstation to '10.81.20.19' as their prefered ...
    (microsoft.public.windows.server.active_directory)
Loading