The implications of AI and machine learning in cyber security are massive and constantly growing, creating both efficiencies and new challenges across the board. Check out our on-demand webinar to learn more about how AI can help your organization!
RRAS not getting IP addresses from DHCP
Hi,
Strange problem. Up until yesterday my Routing and Remote Access was working perfectly. I had it setup to use the DHCP server, on the same machine, to give out IP addresses to VPN clients and had no issues. VPN clients would get an IP in the 192.168.2.x range and from there would be able to access shared folders etc.
All of a sudden, beginning on Monday morning, VPN clients are now getting IP addresses of 169.254.x.x - I'm aware that this is a AIPIA address and I can see that ipconfig /all gives me Dhcp.....No
My DHCP server is running fine and giving out addresses internally on the LAN. I've checked the config of RRAS and it is configured to use the IP of my DHCP server.
Anyone any ideas on this? Need to get sorted ASAP!!
Thanks,
Patrick.
Strange problem. Up until yesterday my Routing and Remote Access was working perfectly. I had it setup to use the DHCP server, on the same machine, to give out IP addresses to VPN clients and had no issues. VPN clients would get an IP in the 192.168.2.x range and from there would be able to access shared folders etc.
All of a sudden, beginning on Monday morning, VPN clients are now getting IP addresses of 169.254.x.x - I'm aware that this is a AIPIA address and I can see that ipconfig /all gives me Dhcp.....No
My DHCP server is running fine and giving out addresses internally on the LAN. I've checked the config of RRAS and it is configured to use the IP of my DHCP server.
Anyone any ideas on this? Need to get sorted ASAP!!
Thanks,
Patrick.
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
LVL 20
If you DHCP server is not full I would start the DHCP Server Service and try again. Still no go I would open RRAS Config and delete and recreate the DHCP Relay Agent settings. You need this even if the VPN server and DHCP server are they same box.
Should have mentioned that I've tried both of those along with restarting the server. Should also have mentioned it's a Win2003 SBS server too.
Any other ideas?
Any other ideas?
Well at this point I would reset the config for RRAS and rebuild it. If that does not work rebuild the DHCP which both should take about 5 minutes. Also fro DHCP set it with conflict detect at 2:
Right click on DHCP server select properties then select the Advanced tab and select 2 for Conflict detect.
Right click on DHCP server select properties then select the Advanced tab and select 2 for Conflict detect.
As this is Small Business Server run the Configure Remote Access within Server Manager todo list and check make sure all the settings are correct.
This will reset everything and make sure it's all working correctly.
This will reset everything and make sure it's all working correctly.
I have already reset and rebuilt RRAS and DHCP to no avail and I cannot run the config wizard successfully as I only have 1 network card on the server.
Here's the PPP adapter details from a connected client. As you can see I'm getting the correct DNS server, but not the correct IP. Any more ideas?
PPP adapter Clancy VPN:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 169.254.223.20
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.2.252
Here's the PPP adapter details from a connected client. As you can see I'm getting the correct DNS server, but not the correct IP. Any more ideas?
PPP adapter Clancy VPN:
Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface
Physical Address. . . . . . . . . : 00-53-45-00-00-00
Dhcp Enabled. . . . . . . . . . . : No
IP Address. . . . . . . . . . . . : 169.254.223.20
Subnet Mask . . . . . . . . . . . : 255.255.255.255
Default Gateway . . . . . . . . . :
DNS Servers . . . . . . . . . . . : 192.168.2.252
Yep, even though I have checked the settings for TCP/IP on that VPN connection and they are set to Obtain an IP address automatically. If I try and force it to use a specific IP, eg. 192.168.2.142 (which I know is free on the LAN) then I get an error connecting the VPN that the server has rejected the IP.
Have a look at this thread here for configuring VPN on SBS
You should still be able to run through the wizard with one NIC as long as you have completed the connect to internet wizard with the 1 nic option
You should still be able to run through the wizard with one NIC as long as you have completed the connect to internet wizard with the 1 nic option
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trial
sorry forgot the link: http://www.chicagotech.net/netforums/viewtopic.php?t=55
OK, I ended up moving routing and remote access to another server, which had 2 NICs, and I am now getting correct IP addresses.
However, I cannot ping my original server - 2.252, when connected over the VPN unless I check the option to Use Default Gateway on Remote Netowrk op the VPN client PCs. This would prevent their internet from working though so not an option. When I uncheck Use Default Gateway I can no longer ping the 2.252 server.
Anyone any thoughts??
However, I cannot ping my original server - 2.252, when connected over the VPN unless I check the option to Use Default Gateway on Remote Netowrk op the VPN client PCs. This would prevent their internet from working though so not an option. When I uncheck Use Default Gateway I can no longer ping the 2.252 server.
Anyone any thoughts??
Is the default gateway and different on the 2.252 server? Can the server ping the workstation when connected to the VPN?
I ended up adding a route on the firewall for VPN traffic pointing it to the 2.252 server and all now wroking. Don't know how or why but there you go..
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
SBS
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.