Whats New in the .NET Framework Version 3.5::
This topic contains information about new and enhanced features in the .NET Framework version 3.5.  Provides a simple way to check whether an Authenticode signature is
http://msdn.microsoft.com/en-us/library/bb332048.aspxHOME |
I am wondering if Outpost v.2.1 can be instructed to "trust" a specific remote IP.
I would like to see what ports, if any, are being protected by my ISP. I understand that if I can somehow temporarily instruct the firewall to trust the ShieldsUP! probe IP of [204.1.226.228], I may be able to determine which port/s are protected by my ISP.
Another way to learn: case studies; 2007::
Clearly there is much to be done and a test of a fair. society is whether the most a way to promote a sense of responsibility among. participants with
http://unesdoc.unesco.org/images/0015/001518/151825e.pdfHOME |
As it is now, ShieldsUP! indicates ports 1-1056 are fully stealthed. However, some of those ports may protected by bigzoo.net (ISP).
Regards,
Best FTP Server - DonationCoder.com::
Going through them one page at a time is a good way to get it all set up. It comes with a remote server administration program, and there is an optional
http://www.donationcoder.com/Reviews/Archive/FtpServer/index.htmlHOME |
Enterprise Java Community: Under the Hood of J2EE Clustering::
Load balancing is one of the key technologies behind clustering, which is a way to obtain Shown as figure 4, a browser may call a remote JSP object through HTTP protocol.
http://www.theserverside.com/tt/articles/article.tss?l=J2EEClusteringHOME |
Ricardo
If Outpost sees it, it logs it - but some logs at excessive attack rates may be dropped.
If Outpost didn't log it, then your ISP may be blocking it - I'll check, since I KNOW my ISP blocks some.
Just took a "Common Ports" scan, and OP logged everything (in blocked), except 135, 139, 445 - ports which I DO know the ISP blocks to prevent RPC-attack and similar worms spreading.
Simple - add the IP address to your LAN settings and check the Trusted box. All traffic to and from this address will now be allowed (as detailed in the Outpost Rules Processing Order (http://www.outpostfirewall.com/forum/showthread.php?s=&threadid=8394) FAQ thread).
MTDay & P2k,
Thanks for the quick response. I placed the ShieldsUP! address in the LAN settings, as instructed. The result was all of the ports between 1-1056 were CLOSED except for the following three:
Port 135 (epmap)
DCE endpoint resolution
Port 445 (microsoft-ds)
Microsoft Directory Service
Port 1025 (ms-svchost)
Microsoft Generic Service Host
which were OPEN.
Also, when I did the ports scan with ShieldsUP! as a trusted site, I received my first ever warning from Outpost re: Attack Detection Report!
As soon as I reverted to my previous settings, OP v.2.1 STEALTHED all ports 1-1056. Now all is right in the universe, again.
Thanks for assisting me to determine for myself the level of protection OP v.2.1 is giving my system.
BTW PC Flank returned a clean bill of health for TCP and SYN testing, as well.
Ricardo :cool:
 Get Smart About Monitoring Virtual Machines
 Microsoft Gets Ex-Streamly Cozy with U.K.'s MediaWave
|
Is there a way to "trust" a specific remote IP