[AF] After configuring NAT, access to the intranet WEB server fails, but intranet access is normal
Problem Description
AF configured with Destination NAT, access to the intranet web server is unavailable, but intranet access is normal
Warning Info
Accessing the web page reports a 404 error

Effective troubleshooting steps
- Check that Destination NAT Policies and that the external network telnet test port can be accessed.
- Open direct test
- The intranet access Business Asset Address test can be accessed normally
- Capture packets on both the internal and external network ports of the AF device to check that NAT is normal, the three-way handshake is normal, and a 404 is returned after accessing the HTTP page GET request

- Use the tool to modify the host field in the HTTP request header to Services server private network address to simulate the access test, and you can jump to the server page


- Coordinate with the server vendor to check the server configuration and set restrictions on the server middleware. After adjustment, access is normal.
Root cause
Services server itself has restrictions on the host field in the HTTP request header
solution
By adjusting the middleware settings on the server, access is normal after the restrictions are lifted
Original Link
https://support.sangfor.com.cn/cases/list?product_id=13&type=1&category_id=1322&isOpen=true