NOT!I have already assigned static addresses so at least the network works while we can hopefully come up with some kind of fix.I discovered the problem following a lease expiring which Can not start the DHCP Service in Windows SBS 2003 ? That method will take forever and a day, but if no one can think of another solution, that may be our only option! 0 Datil OP Chris Seiter So it looks like it's not a network switch error The only thing I can think of is there's a rouge device on our network that's handing out DHCP as well? http://johnfladung.net/sbs-2003/sbs-2003-rww-not-working.html
If your client cannot obtain an IP address is will fail back to an APIPA address in the 169.254.x.x subnet. You could also install wireshark or similar on the SBS and a test laptop to get visibility of the dhcp requests. If that's pointing to the wrong address, you will see the symptoms you are seeing. What am I doing wrong?
The server then automatically forwards requests it cannot resolve locally. It is recommended to add longer leases for a fixed network (in the office for example) and shorter leases for remote connections or laptop computers. The issue might be on the NAT config. __________________ Networking Articles & Tutorials Preposting Requirements 05-05-2010, 10:32 AM #7 djaburg Moderator - Microsoft Support Join Date: May ISA firewall is a good example.
This is because ISA will try to resolve the broadcast IP to a URL to make sure it is not blocked. That's the quickest way to have an issue. Cheers __________________ Knowledge is our most powerful weapon. 04-30-2010, 02:07 AM #3 jithinkcs Registered Member Join Date: Apr 2010 Posts: 16 OS: XP SP2 Hai , I found Find a client PC and try and obtain an IP address through DHCP.
A couple of months ago I rolled a second domain controller on a client's network and configured it to serve DNS and DHCP. This new range also saves me from having to put in a reservation for the printer at 192.168.1.13. Try this article and recheck everything:http://www.microsoft.com/technet/isa/2004/plan/isaondhcpserver.mspx 0Votes Share Flag Collapse - Thanks by feitosa · 8 years ago In reply to DHCP Eventually DHCP of my SBS stopped working. It is now time to set the lease duration for how long a client can use an IP address assigned to it from this scope.
Request has timed out. 0 LVL 38 Overall: Level 38 Windows Server 2003 33 SBS 9 DHCP 7 Message Expert Comment by:ChiefIT2008-06-19 Comment Utility Permalink(# a21826858) I did mention zeroed There is only one NIC (so it appears) available (not bridged under network connections). To do this, I recommend that you do not allow the DHCP server to provide leases within a range of IPs. Tuesday, April 01, 2008 12:26 AM Reply | Quote 0 Sign in to vote wrness,Good problem eh?
Followed by the change of ip address, I also added the new subnet to AD sites and services, change DNS and change DHCP scope. weblink and staring at it lots! 2 Mace OP Martin2012 Jan 9, 2012 at 11:14 UTC I'd also check no other dhcp server is sitting out there. Carl Hoogstoel C4 Consulting 0 Message Active 6 days ago Author Comment by:haident2008-07-09 Comment Utility Permalink(# a21969417) press2esc: I checked the three registry keys you mentioned, but they all have second start with the simples and work your way into the problem.
On your Netopia, you still have an issue. This was exactly what was wrong with me --> 1. P2E 0 Message Active 6 days ago Author Comment by:haident2008-06-16 Comment Utility Permalink(# a21797334) Press2Esc, Your post makes no sense to me. http://johnfladung.net/sbs-2003/sbs-2003-dns-not-working.html I found it .
On the LAN side of your router, your prefered DNS servers should be your internal DNS server, not outside DNS servers. by MDD on Mar 12, 2012 at 9:42 UTC | Networking 0Spice Down Next: Unable to ping static IP from DHCP clients on same subnet TECHNOLOGY IN THIS DISCUSSION Join the Right now, you are going outside your LAN for DNS.
I've seen cases where the users bring in their own wireless due to the IT admin's onerous rules and it causes havoc. One other thing, are you getting APIPA addresses (169.xxx.xxx.xxx addresses) In this example I have excluded a range of IP addresses, 10.0.0.100 to 10.0.0.110, and a single address, 10.0.0.150. Check your switch for changes to the Vlan i.e. It does.
There does not seem to be a physical problem, as I can set a static IP address that will work just fine. In DNS, that's called the scope, and you may have told SBS to hand out 120 addresses, and you've now filled up that list.