Please select To the mobile version | Continue to access the desktop computer version
 Forgot password?
 Register now


Router

View: 2565|Reply: 1

The PC in LAN fails to access the internal server by server's domain name.

[Copy link]

10

Digests

994

Posts

1107

Credits

administrator

Rank: 9Rank: 9Rank: 9

Credits
1107
Post time 2017-5-4 18:57:50 | Show all posts |Read mode
The PC in LAN fails to access the internal server by server's domain name.
Reply

Use magic Report

10

Digests

994

Posts

1107

Credits

administrator

Rank: 9Rank: 9Rank: 9

Credits
1107
 Author| Post time 2017-5-4 18:58:19 | Show all posts
1. Test whether the public IP address mapped to the domain name is accessible and whether the domain name is successfully resolved to the public IP address.

2. The permit-inside feature should be configured on the Internet NAT router.

3. Test whether the PC on the intranet can access the internal server by using an internal IP address to confirm whether the problem is due to an exception of the intranet or the server.

4. Check whether policy-based routing (PBR) is applied to the internal network port on the Internet NAT router. If yes, configure the PBR ACL to reject the traffic generated by access to the internal server by the intranet PC.

Example:
R1(config)#ip access-list extended 110       //ConfigureACL 110 mapped to PBR.
R1(config-ext-nacl)#10 deny ip 172.16.1.0 0.0.0.255 172.16.2.0 0.0.0.255    //Configure the PBR ACL to reject the traffic generated by access to the internal server(172.16.2.0/24) from the intranet IP address 172.16.0.0/24.
R1(config-ext-nacl)#20 permit ip 172.16.1.0 0.0.0.255 any     //Match the traffic generated by access to the Internet from the intranet IP address 172.16.1.0/24.

Reply Support Not support

Use magic Report

You have to log in before you can reply Login | Register now