Hi all outpost people and thank for your help (hope).
I have recurent problem, i use OP2.5/370 and i load all recommandations and preset rules of Paranoid2000, i have disabled DNS resolution (udp and tcp) and write in preset.lst my DNS and DHCP adress.
All work fine and i can see in application the secure SVCHOST rule.
But at next boot, OP cannot find my IP adress (it find 169.xxx). I cannot have connection, when i disabled secure SVCHOST and reboot, OP find my good IP adress (82.xxx).
I 've read some post about DHCP problem. anyone have suggestion ??
Thank a lot for yours answers and sorry for my poor english (from PARIS...)
Thank you for all this precision Paranoid2000, the fact is that i wait not a couple of minute, but ip is looked on 169.xxx...
JBoss - Java Application Server::
Cannot find message resources under key org apache struts action MESSAGE html?module bb&op viewtopic&p 3874451#3874451 This From Localhost to IP adress
http://www.junlu.com/8_872.htmlHOME |
the symptom is very funny, when i use secure SVCHOST, ip is looked on 169.xx and no possible connection, when i deleted the svchost rule and boot, ip is logged on my good adress (82.xxx) until OP ask me that generic host process want a connection with secure SVCHOST etc,....
When i look the bloked traffic, i see that OP stop the procedure (RPC)(TCP).
I use adsl with freebox.
Thank for all suggestion, and special thank yet to paranoid2000
did's
Did's,
With the secure rules for DHCP, it is quite possible that your PC will take longer to gain an IP address since some of the DHCP traffic does get blocked. I would suggest waiting a couple of minutes (keeping an eye on the Outpost Network Activity window) - when ICMP Router Solicitation packets are reported (and blocked) an IP address is usually picked up a few seconds later.
If you consider this delay unacceptable, then by all means remove the restrictions from the svchost DHCP rule. The balance between security and convenience is one only you can decide. :)
Whith more analyse, i think it's BOOTPS in cause.
When i have secure SVCHOT, OP stop traffic when i boot the pc and give me 169.xxx in IP adress, i can see that BOOTPS was stopped.
When i deleted svchost rule and reboot the pc, i can see that OP pass BOOTPS, and OP give me my correct IP adress, until Generic Host Process need out connection with secure SVCHOST, if i say ok, no problem until next boot and "re-belotte" (special french idiom).
Hope that this precision can help the Outpost communauty to help me, thank a lot for your future suggestions.
Did's
When i have secure SVCHOT, OP stop traffic when i boot the pc and give me 169.xxx in IP adress, i can see that BOOTPS was stopped.A 169.x.x.x address is used when DHCP has failed - however Windows will keep checking for DHCP and you should find that a proper IP address is picked up as long as you have specified the correct DHCP server address in your svchost DHCP rule.
Having the right address is critical and if you are on dialup, you may find that this address keeps changing. The only option then is to remove the address restriction on the rule (as the Guide suggests) and to keep checking it on subsequent logins to see if there is any pattern (e.g. if the address is always in the range 204.112.93.1-254, you could use the wildcard 204.112.93.* in your svchost rule).
 Microsoft Unleashes Visual Studio .NET
 IBM's iPhrase Buy Adds to WebSphere
|
OP cannot find my IP adress