I use router and remote access to implement this,but fail. How to do it? Please tell me how to implement it from "routing and remote access" in detail. I dont want use netsh. Thursday, March 20, AM. Hi, I think this will not work. Source IP and port number this port is a randomly generated Destination IP and port SQL by default So we cannot control which port to use when connecting another service.
Thursday, March 27, AM. Feedback will be sent to Microsoft: By pressing the submit button, your feedback will be used to improve Microsoft products and services. Privacy policy. This step-by-step guide describes how to set up a Routing and Remote Access service on Windows Server Standard Edition or Windows Server Enterprise Edition to allow authenticated users to remotely connect to another network by way of the Internet.
This secure connection provides access to all internal network resources, such as messaging, file and print sharing, and Web server access. The remote character of this connection is transparent to the user, so the overall experience of using remote access is similar to that of working at a workstation on a local network.
By default, the Routing and Remote Access service is installed automatically during the Windows Server installation, but it is disabled. If the icon has a red arrow in the lower-right corner, the Routing and Remote Access service isn't enabled. Go to step 3. For a green arrow pointing up in the lower-right corner, the service is enabled. If so, you may want to reconfigure the server.
To reconfigure the server, you must first disable Routing and Remote Access. You may right-click the server, and then click Disable Routing and Remote Access.
Click Yes when it is prompted with an informational message. This doesn't solve it at the network layer as RRAS does, but it does solve it without resorting to 3rd party software. Since only the localhost will pass through the RRAS filter, addressing this at the software layer is not an issue.
Other options. If you are accessing by name, you can put an entry in the local hosts file on the RRAS server pointing the name to the interal ip. If you are accessing by IP, you should be able to put in a static route that says route publicip through privateip.
The server at privateip should see the packet say "hey, that's me" and handle it appropriately, although you might require a route on the other side to get packets back correctly depending on your network setup. Sign up to join this community. The best answers are voted up and rise to the top.
Stack Overflow for Teams — Collaborate and share knowledge with a private group. Create a free Team What is Teams? Learn more. Asked 12 years, 1 month ago. Cause : The VPN connection doesn't have the appropriate permissions through dial-in properties of the user account and remote access policies. Solution : Verify that the VPN connection has the appropriate permissions through dial-in properties of the user account and remote access policies.
For the connection to be established, the settings of the connection attempt must:. For more information about an introduction to remote access policies, and how to accept a connection attempt, see the Windows Server Help and Support Center. Cause : The settings of the remote access policy profile are in conflict with properties of the VPN server.
The properties of the remote access policy profile and the properties of the VPN server both contain settings for:. If the settings of the profile of the matching remote access policy are in conflict with the settings of the VPN server, the connection attempt is rejected. Solution : Verify that the settings of the remote access policy profile aren't in conflict with properties of the VPN server. Cause : The answering router can't validate the credentials of the calling router user name, password, and domain name.
Solution : Verify that the credentials of the VPN client user name, password, and domain name are correct and can be validated by the VPN server. Solution : If the VPN server is configured with a static IP address pool, verify that there are enough addresses in the pool.
If all of the addresses in the static pool have been allocated to connected VPN clients, the VPN server can't allocate an IP address, and the connection attempt is rejected. If all of the addresses in the static pool have been allocated, modify the pool. Solution : Verify the configuration of the authentication provider. Solution : For a VPN server that is a member server in a mixed-mode or native-mode Windows Server domain that is configured for Windows Server authentication, verify that:.
If not, create the group and set the group type to Security and the group scope to Domain local. You can use the netsh ras show registeredserver command to view the current registration.
You can use the netsh ras add registeredserver command to register the server in a specified domain. To immediately effect this change, restart the VPN server computer. For more information about how to add a group, how to verify permissions for the RAS and IAS security group, and about netsh commands for remote access, see the Windows Server Help and Support Center.
If not, type the following command at a command prompt on a domain controller computer, and then restart the domain controller computer:. For more information about Windows NT 4. For more information about how to add a packet filter, see the Windows Server Help and Support Center.
Cause : The appropriate demand-dial interface hasn't been added to the protocol being routed. Solution : Add the appropriate demand-dial interface to the protocol being routed. For more information about how to add a routing interface, see the Windows Server Help and Support Center. Cause : There are no routes on both sides of the router-to-router VPN connection that support the two-way exchange of traffic.
Create routes on both sides of the router-to-router VPN connection so that traffic can be routed to and from the other side of the router-to-router VPN connection. You can manually add static routes to the routing table, or you can add static routes through routing protocols. For more information about how to add an IP routing protocol, how to add a static route, and how to perform auto-static updates, see Windows Server online Help.
0コメント