I have 2 sites, one router & one switch per site. There is connectivity between the two sites on the fiber interface. The routing method is EIGRP and is configured correctly. The routes are being updated in the routing table and I can ping any IP address from either side (including the remote DHCP server). Show Here is my problem: connecting on the access port of the switch I am unable to get an IP address from the DHCP server on the other site. I have the interface for the VLAN to be using an ip helper-address on the opposite side andddd nothing. I thought maybe it was because it was sharing the same IP pool, so I created a pool that matched the subnet to hand out leases. Still not working. I've attached the full devices config with redacted passwords on the site to site setup here with Router1, Switch1, Router2 & Switch2. Mind you, everything else in the configuration works minus the DHCP relay. If someone could tell me why I cannot get my ip helper-request to forward into a remote site, I would greatly appreciate it and probably owe you a beer. Upgrade to Microsoft Edge to take advantage of the latest features, security updates, and technical support. Identify and resolve Remote Access server operations problems
In this articleApplies To: Windows Server 2012 R2, Windows Server 2012 Note: Windows Server 2012 combines DirectAccess and Routing and Remote Access Service (RRAS) into a single Remote Access role. You can using the following procedures to identify Remote Access server operations issues, their root causes, and the resolution required to fix the issues. Note You must be signed in as a member of the Domain Admins group or a member of the Administrators group on each computer to complete the tasks described in this topic. If you cannot complete a task while you are signed in with an account that is a member of the Administrators group, try performing the task while you are signed in with an account that is a member of the Domain Admins group. This topic includes information about performing the following tasks: Simulate an operations issue Identify the operations issue and take corrective action Restore the IP Helper service Simulate an operations issueWarning Because your Remote Access server is probably configured properly and not experiencing any issues, you can use the following procedure to simulate an operations issue. If your server is currently servicing clients in a production environment, you may not want to take these actions at this time. Rather, you can read through the steps to understand how to address issues that might arise on your Remote Access server in the future. The IP Helper service (IPHlpSvc) hosts IPv6 transitioning technologies (such as IP-HTTPS, 6to4, or Teredo), and it is required for the DirectAccess server to function properly. To demonstrate a simulated operations issue on the Remote Access server, you must stop the (IPHlpSvc) network service. To stop the IP Helper service
Identify the operations issue and take corrective actionTurning off the IP Helper service will cause a serious error on the Remote Access server. The monitoring dashboard will show the operations status of the server and the details of the issue. To identify the details and take corrective action
Restore the IP Helper serviceTo restore the IP Helper service on your Remote Access server, you can follow the Resolution steps above to start or restart the service, or you can use the following procedure to reverse the procedure that you used to simulate the IP Helper service failure. To restart the IP Helper service on the Remote Access server
.jpeg)Windows PowerShell equivalent commands The following Windows PowerShell cmdlet or cmdlets perform the same function as the preceding procedure. Enter each cmdlet on a single line, even though they may appear word-wrapped across several lines here because of formatting constraints. |