Marc
02-15-2004, 06:51 AM
Hi all,
I've a problem with my home network (2 Win XPpro PCs).
With the (default) gateway PC it is no problem to connect to the internet. The other (network) PC can connect to the gateway PC (including http) and ping web servers in the internet but it is not possible to surf in the web. It seams that the packets can go out (first line in the log) but the http answer cannot come back (something like "blocked transit packets" in the second log line).
If the Outpost FW is off on the gateway PC the routing is fine and I can use the web from the network PC...
Both PCs running Win XP pro SP1 + all updates, Outpost v2.0.238.3121 (290) Family license
network PC: 10.0.0.42/255.255.255.0
default gateway: 10.0.0.10/255.255.255.0
and one from the Internet provider
The Internet connection on the gateway is done by AVM Blue Fritz ISDN (over Bluetooth to the telephone-ISDN-box)
What rule is missing or wrong? I tryed it with something like enable all for 10.0.0.42 (in and out)
Marc
I've a problem with my home network (2 Win XPpro PCs).
With the (default) gateway PC it is no problem to connect to the internet. The other (network) PC can connect to the gateway PC (including http) and ping web servers in the internet but it is not possible to surf in the web. It seams that the packets can go out (first line in the log) but the http answer cannot come back (something like "blocked transit packets" in the second log line).
If the Outpost FW is off on the gateway PC the routing is fine and I can use the web from the network PC...
Both PCs running Win XP pro SP1 + all updates, Outpost v2.0.238.3121 (290) Family license
network PC: 10.0.0.42/255.255.255.0
default gateway: 10.0.0.10/255.255.255.0
and one from the Internet provider
The Internet connection on the gateway is done by AVM Blue Fritz ISDN (over Bluetooth to the telephone-ISDN-box)
What rule is missing or wrong? I tryed it with something like enable all for 10.0.0.42 (in and out)
Marc