|
-
Feb 9th, 2011, 06:11 AM
#1
Thread Starter
Addicted Member
Internet transfer control (msinet.ocx) and windows firewall
Internet transfer control is freely going through windows firewall, why?
-
Feb 9th, 2011, 06:18 AM
#2
Re: Internet transfer control (msinet.ocx) and windows firewall
Most firewalls are set to allow outbound connections on HTTP and HTTPS default ports (80, 443). Some firewalls are happy to let any outbound connection go through.
The main thing to block is inbound connections, though right after that you get suspicious about trojans that phone home so outbound protection can be important too.
If you use the ITC with FTP it can be another story, since default operation (PORT mode) means you connect out on one port but the server connects back on a second one. PASV mode FTP exists for when you need to have both "channels" (control and data) connect outward from the client. I don't recall whether the ITC supports PASV mode.
-
Feb 9th, 2011, 07:04 AM
#3
Thread Starter
Addicted Member
Re: Internet transfer control (msinet.ocx) and windows firewall
Thank you. What a terrible default rules for the firewalls 
-
Feb 9th, 2011, 08:34 AM
#4
Re: Internet transfer control (msinet.ocx) and windows firewall
 Originally Posted by pantalone
Thank you. What a terrible default rules for the firewalls  
Why do you think so? Otherwise browsers, web services, etc. would never work without users manually tweaking firewall rules.
I don't know of too many corporate networks that block things like outgoing HTTP requests. Why does it make sense for your computer to?
Maybe you aren't sure what a firewall is for?
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|