• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 851
  • Last Modified:

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?
0
GibsonGuitarIT
Asked:
GibsonGuitarIT
  • 4
  • 4
1 Solution
 
rat3ideaCommented:
Make Sure your DHCP Relay is setup on the Internal NIC of the ISA 2006 Server. If that is not it could you post the error from the event viewer?

Thanks!
0
 
GibsonGuitarITAuthor Commented:
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
0
 
rat3ideaCommented:
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"
0
Will You Be GDPR Compliant by 5/28/2018?

GDPR? That's a regulation for the European Union. But, if you collect data from customers or employees within the EU, then you need to know about GDPR and make sure your organization is compliant by May 2018. Check out our preparation checklist to make sure you're on track today!

 
GibsonGuitarITAuthor Commented:
It's Windows Server 2003 R2, but I did check everything just to be sure...all of the above checks out.
0
 
rat3ideaCommented:
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.
0
 
GibsonGuitarITAuthor Commented:
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.
0
 
rat3ideaCommented:
I am assuming at this point you tried to restart the ISA Server? Or if you cannot, at least restart the RRAS Service.
0
 
GibsonGuitarITAuthor Commented:
Of course, that was the first thing I tried.  When all else fails...reboot :)

As it happens, I resolved the issue.  I'm not sure how or why, but the policy I had set up to allow DHCP\BOOTP traffic had simply "stopped working."  I created a new one, allowing dhcp from all networks to all networks, and the issue disappeared.

Thanks for the help!
0

Featured Post

Learn to develop an Android App

Want to increase your earning potential in 2018? Pad your resume with app building experience. Learn how with this hands-on course.

  • 4
  • 4
Tackle projects and never again get stuck behind a technical roadblock.
Join Now