Often, an IP address is hidden behind a proxy or NAT. Here is how you can tell the public IP:
The Blue Coat Proxy / Filter device transfers packets like any other network device. A simple troubleshooting technique is to see if the packets are flowing through the device as expected. Here are the commands to do a Blue Coat Packet Capture:
A common step in troubleshooting is finding out what not to troubleshoot. With a packet capture you can confirm things such as routing, firewall rules, and remote services.
Using Telnet to Test Open Ports
The Setup on Digitalcrunch.com:
- 5555 is blocked via a firewall
- 80 is open and running http service
- 22 is open and running ssh
How to Manually Use Telnet
Typing anything and then hitting enter is like sending protocol information to the remote service. If you know the protocol and it accepts ascii, you can manually interact. If not, it will give you an error message. You can’t type binary data this way though.
Example of Telnet Error Message
C:\>telnet digitalcrunch.com 22
Example of Manually Typing ASCII protocol
C:\>telnet digitalcrunch.com 80 GET /index.php HTTP/1.1 host: digitalcrunch.com <enter>
Example of Blocked Port:
C:\>telnet digitalcrunch.com 5555
No Service exists on server:
For example, the database team wants to test if they can get to digitalcrunch.com on port 8888, however, the server isn’t provisioned yet – but they still want you to test! In this example, I have opened the firewall to port 8888, but there is nothing listening on that port. Compare to the “blocked port” above to see the difference.
C:\>telnet digitalcrunch 8888 Connecting To digitalcrunch.com...Could not open connection to the host, on port 8888: Connect failed
The windows firewall is actually pretty good at blocking inbound traffic, and even outbound traffic if configured properly. The interface is horrible though! You can get to the control panel by typing wf.msc, but you can also disable windows firewall from the cli. Here are some other useful commands: