|
This is a multipart message in MIME format. -- [ Picked text/plain from multipart/alternative ] Hi Jon, Here is my CDN$0.02.. I think that you will find that is how most of the consumer hardware router/firewall devices work. They should block unsolicited inbound connections unless you have it configured otherwise. This blocks a lot of indirect attacks via open ports. As has been pointed out locally it will not protect you if you are using some sharing application that bypasses the firewall (KaZa et. al.). As an aside I found that my eldest was running Morpheus on his Win95 system because it would hang the LinkSys router. With the LinkSys I believe that you can configure it to have a "trigger port" that if activated with an outbound connection then the LinkSys would automatically allow an inbound connection on another port (4200 in your case). Kind regards, Mike Mike Hockings, P.Eng. WebSphere Development Tools for AS/400 - CODE/Designer & WebFacing ! IBM Canada Ltd. Laboratory hockings@ca.ibm.com "Jon Paris" <Jon.Paris@Partner400.com> Sent by: code400-l-admin@midrange.com 10/10/2002 01:18 PM Please respond to code400-l To: <code400-l@midrange.com> cc: Subject: Long Story >> That's interesting as I have had the opposite experience (though I admit I may be missing something besides the CODE help system). I don't understand firewalls etc. but they do seem to figure in the picture here. When working from my home office via a DSL connection (and LinkSys router) I can get autostart servers to work just fine. STRCODE will not work unless I open port 4200 on the firewall in the router. I have made the assumption (which seems to be born out by experiments that I and others have made) that at least the LinkSys unit will allow inbound messages to a port if that port (4200) initiated the conversation. What it will not do is accept incoming traffic on that port unless it is unlocked. This has been my experience anyway - does it match yours? Jon Paris Partner400 _______________________________________________ This is the CODE/400 Discussion & Support (CODE400-L) mailing list To post a message email: CODE400-L@midrange.com To subscribe, unsubscribe, or change list options, visit: http://lists.midrange.com/cgi-bin/listinfo/code400-l or email: CODE400-L-request@midrange.com Before posting, please take a moment to review the archives at http://archive.midrange.com/code400-l. NOTE: WDSc for iSeries disucssion has it's own mailing list. Information can be found at http://lists.midrange.com/cgi-bin/listinfo/wdsc-l
As an Amazon Associate we earn from qualifying purchases.
This mailing list archive is Copyright 1997-2024 by midrange.com and David Gibbs as a compilation work. Use of the archive is restricted to research of a business or technical nature. Any other uses are prohibited. Full details are available on our policy page. If you have questions about this, please contact [javascript protected email address].
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.