Antecedents:
The hinemos server was migrated from the local data center to aws two days ago.
After the migration is complete, after some settings, all monitoring items can be monitored normally.
After all the settings are completed, set up a security group for the hinemos server, as follows:
1. All sources (0.0.0.0/0) can pass through port 8080 of this instance (inbound)
2. Only the 22 port (inbound) of the company ( XXX. XXX. XXX. XXX /32) is opened
Connect to the HinemosServer from the local again and find that there is no problem.
I thought it was a success, but after sending the address to connect to the HinemosServer to the client, the client said that the connection could not be successful.
Failed to access the WSDL at: http://XXX.XXX.XXX.XXX:8080/HinemosWSAccessEndpointService?wsdl. It failed with:Got http://XXX.XXX.XXX.XXX:8080/HinemosWSAccessEndpointService?wsdl while opening stream from http://XXX.XXX.XXX.XXX:8080/HinemosWSAccessEndpointService?wsdl.
go through:
Therefore, the phenomenon was investigated from the following aspects.
1. Local wired and wireless (different ip) can be accessed normally
2. It is also possible to access from an aws instance in Tokyo area.
Through the above two points, it is concluded that there is no problem with my settings, so I guess that the port 8080 on the user's side may be banned.
3. Close the exit of 8080 in Tokyo District, connect again and find the same error as above.
in conclusion:
So I came to the conclusion, because the port 8080 exported by the customer is banned
How to let customers use a simple method to determine whether port 8080 is banned?
Enable windows telnet service
Control Panel-"Programs-"Programs and Features-"Turn Windows features on or off, find the telnet client and turn it on.
Open the windows command line and execute telnet XXX.XXX.XXX.XXX 8080
If the outgoing 8080 port is open, this will jump to another black box.
If the outgoing port 8080 is closed, it will always be connected. . . this state.