GibsonGuitarIT
asked on
ISA 2006 not giving out IP addresses to VPN Clients?
Hi everyone,
All of a sudden, our ISA 2006 has stopped giving out the proper addresses. Instead, it's giving out addresses in the 169.254.x.x range...which seems to suggest that it's lost connectivity to dhcp. However, in the dashboard, DHCP connection shows as good. Nothing changed that I know of, but this is becoming something of a hot issue.
Any thoughts?
All of a sudden, our ISA 2006 has stopped giving out the proper addresses. Instead, it's giving out addresses in the 169.254.x.x range...which seems to suggest that it's lost connectivity to dhcp. However, in the dashboard, DHCP connection shows as good. Nothing changed that I know of, but this is becoming something of a hot issue.
Any thoughts?
ASKER
Unable to contact a DHCP server. The Automatic Private IP Address 169.254.86.28 will be assigned to dial-in clients. Clients may be unable to access resources on the network.
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
That's all the event viewer has to say
For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.
That's all the event viewer has to say
Resolutions:
1) If this is XP, obtain the latest service pack for Windows XP.
2) Use the Network Diagnostics tool to identify any failed settings. To do this, go to Help and Support>Use Tools to view your computer information and diagnose problems>Network Diagnostics>Scan your system. When the process finishes, check for any items marked "FAILED" in red, expand those categories, and view the additional details about what the testing showed.
3) Assign a static ip on the client and ping the DHCP server. If you can't ping the DHCP server, check the connection and hardware.
4) If you can ping the DHCP after assigning static ip, check the DHCP settings.
5) Make sure no firewall is running on your LAN.
6) Run Repair this connection if it is XP. Or use netsh to reset TCP/IP configuration.
7) If it is win98/w2k, remove and reinstall TCP/IP.
8) Try to upgrade the new NIC driver.
9) Make sure you don't run out of IPs in the DHCP scope.
10) If you use a router as DHCP, you may want to upgrade the firmware.
quoted from "ChicagoTech.com"
1) If this is XP, obtain the latest service pack for Windows XP.
2) Use the Network Diagnostics tool to identify any failed settings. To do this, go to Help and Support>Use Tools to view your computer information and diagnose problems>Network Diagnostics>Scan your system. When the process finishes, check for any items marked "FAILED" in red, expand those categories, and view the additional details about what the testing showed.
3) Assign a static ip on the client and ping the DHCP server. If you can't ping the DHCP server, check the connection and hardware.
4) If you can ping the DHCP after assigning static ip, check the DHCP settings.
5) Make sure no firewall is running on your LAN.
6) Run Repair this connection if it is XP. Or use netsh to reset TCP/IP configuration.
7) If it is win98/w2k, remove and reinstall TCP/IP.
8) Try to upgrade the new NIC driver.
9) Make sure you don't run out of IPs in the DHCP scope.
10) If you use a router as DHCP, you may want to upgrade the firmware.
quoted from "ChicagoTech.com"
ASKER
It's Windows Server 2003 R2, but I did check everything just to be sure...all of the above checks out.
Check out this article as well. http://www.isaserver.org/tutorials/2004dhcprelay.html
I know its for 2004 but it walks you through verifying DHCP Relay is enabled and some troubleshooting steps.
I know its for 2004 but it walks you through verifying DHCP Relay is enabled and some troubleshooting steps.
ASKER
No go, unfortunately.
This was an existing set up that has always worked properly...but at some point, for some reason...it stopped. I ran wireshark on the DHCP server, and I can see DHCP requests coming from the ISA server...but for whatever reason, DHCP isn't replying back....though it responds to normal DHCP requests as expected.
This was an existing set up that has always worked properly...but at some point, for some reason...it stopped. I ran wireshark on the DHCP server, and I can see DHCP requests coming from the ISA server...but for whatever reason, DHCP isn't replying back....though it responds to normal DHCP requests as expected.
I am assuming at this point you tried to restart the ISA Server? Or if you cannot, at least restart the RRAS Service.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
Thanks!