internet access diagnostics tool

[TimTDP]

I have a legitimate application that needs to send a file to the Internet. Occasionally I experience situations when security procedures, e.g firewalls, proxy servers, do their job and prevent the file being uploaded. (I use the http protocol for this.)
I am looking for software diagnostics tool that will inform users what procedure is blocking access to the Internet so that their IT experts can allow access.
I am only concerned with PC’s operating Windows.

 

[guest2013-1]

Well, first off, if you're uploading the file with your program and it does use HTTP, it means port 80, and its very rare that the firewall will block it, so something else might be wrong.

What I've experienced in the past is when you use http to send the file, depending on how the network is setup on the client's side, they might be routing port 80 to a server which accepts and probably responds with web mail or their internal website for outside reps.

You should assess the company's infrastructure and setup. You don't really need a diagnostic tool, your only need is to find out from the techies at the company what their setup is when your utility isn't able to upload to someone with their network.

Some companies disallow any incoming (sniffing) attempts at connecting somewhere. so if your program tries to push a file to someone on the network, and they're behind a router, the router wouldn't necessarily know to who to send the file to, but if the request is from the client to download the file and your program delivers it, it knows where to route it.

I can go on and on, but without anymore specifics I'm just speculating at what can go wrong. Unfortnately I don't think a diagnostic utility would help you

 

[guest2013-1]

Oh, I forgot to mention, the restriction on uploading the file to the internet via http could also be Group Policy rules. I know one of my clients has this annoying policy preventing me from downloading exe's

 

[Conradl]

You going to have a tough time finding this. If it uses HTTP, then as mentioned above, the file upload is being blocked by some sort of web filter. These are designed to prevent remote access (sniffing), and would be configured by the administrator to provide a certain amount of feedback, i.e. if the file was blocked because of a rule etc. To determine remotely would be difficult....

 

[TimTDP]

Thanks for the advice. Much appreciated.
I was hoping for a magic tool that worked as follows:
Check for connection.
Report back that
firewall XYZ blocked connection
or
proxy server not configured
or
sniffer packer ABC prevents connection
etc
Then at least I know what the problem is!

 

[w1z4rd]

Just tunnel your data out Port 80 is often blocked by a firewall on corporate networks (so they can push you out through a content filter like Dansguardian)

Port 22 is almost never blocked so tunnels and SCP is an option.