Archived from groups: microsoft.public.windowsxp.basics,microsoft.public.windowsxp.security_admin (More info?)
Hello,
I'm seeing the following log in my router's packet filtering log:
TCP connection denied from 64.4.19.253:80 to 192.168.0.8:1723
This worries me... since 1723/tcp is a port allocated to MS VPN IP tunneling
(bi-directional).
I don't think it's a problem isolated to hotmail (64.4.19.253) ... but that
it could happen to any standard port 80
web site I access since the local port assignment (ie 1723 in this case) is
apparently unpredictatable. However, this is the only
report in my logs of an event like this... and I've been using the following
configuration for a while.
In my situation, I'm behind 3 routers each with NAT/Firewall/SPI
capabilities, it appears to work most of the time without any degregation to
my incoming internet connection (i.e. routers 98Mbps throughput, ISP
12Mbps) - the hardware seems to take care of NAT handling pretty well in
all other connection situations - hence my concern at this particular
issue....
(incidentally, to avoid further discussion on software firewalls - I've
turned mine off... since I'm only referring to the way the OS works in
relation to the rest of the world - s/w firewalls are useful, but shouldn't
be the "be all & end all" since in real-life useage they let through a lot
of traffic... both ways...)
Is there any way that I can restrict IE to a set range of ports for incoming
traffic ? Or is it purely Open game hunting season across all ports above
1024 for IE ? (And other apps) ?
Steve
Hello,
I'm seeing the following log in my router's packet filtering log:
TCP connection denied from 64.4.19.253:80 to 192.168.0.8:1723
This worries me... since 1723/tcp is a port allocated to MS VPN IP tunneling
(bi-directional).
I don't think it's a problem isolated to hotmail (64.4.19.253) ... but that
it could happen to any standard port 80
web site I access since the local port assignment (ie 1723 in this case) is
apparently unpredictatable. However, this is the only
report in my logs of an event like this... and I've been using the following
configuration for a while.
In my situation, I'm behind 3 routers each with NAT/Firewall/SPI
capabilities, it appears to work most of the time without any degregation to
my incoming internet connection (i.e. routers 98Mbps throughput, ISP
12Mbps) - the hardware seems to take care of NAT handling pretty well in
all other connection situations - hence my concern at this particular
issue....
(incidentally, to avoid further discussion on software firewalls - I've
turned mine off... since I'm only referring to the way the OS works in
relation to the rest of the world - s/w firewalls are useful, but shouldn't
be the "be all & end all" since in real-life useage they let through a lot
of traffic... both ways...)
Is there any way that I can restrict IE to a set range of ports for incoming
traffic ? Or is it purely Open game hunting season across all ports above
1024 for IE ? (And other apps) ?
Steve
Facebook
Twitter
Instagram