So the plot thickens, I think. This is not a BorderManager problem from what
I can tell. It seems to be a Windows XP/Windows firewall/IE problem. I am
just posting this as a follow-up so everyone knows the full story.
I have isolated the behavior now. If I use IE 6 or 7 with the windows
firewall (Ver 1.5) enabled, I get a ton of open close tcp traffic when
requesting some web pages, but not all.. The connections open and close
because the firewall drops packets, but the connections stay in the NAT
table until the connection time out is reached. I now have it set for 1
hour, thanks Mysterious! I am seeing the opening and closing in the windows
firewall log along with a bunch of dropped packets.
If I disable the Windows firewall the problem goes away completely. I can
also use Firefox, with or without the windows firewall on and it works fine
so the issue is only with IE.
I captured traffic to and from the server during a problem request using
both conditions, and saw no real difference between with the firewall
enabled, or not at the server. The packets are being dropped at the client.
I can repeat this using both our BM servers one running 3.9 SP1 on NW
6.5sp7, and the other running 3.7 on NW65SP6, and using multiple Windows XP
machines. It is only effecting certain sites, and is always corrected by
disabling the windows firewall.
Here is an extract from the Windows firewall log showing for dropped
packets, and open/close activity from the web site 66.103.230.30.
www.aquariumwaterfilters.com.
-12-02 11:45:25 CLOSE TCP 10.1.0.242 66.103.230.30 4972 80 - - - - - - - - -
2008-12-02 11:45:25 OPEN TCP 10.1.0.242 66.103.230.30 4973
80 - - - - - - - - -
2008-12-02 11:45:25 CLOSE TCP 10.1.0.242 66.103.230.30 4973
80 - - - - - - - - -
2008-12-02 11:45:25 OPEN TCP 10.1.0.242 66.103.230.30 4974
80 - - - - - - - - -
2008-12-02 11:45:25 CLOSE TCP 10.1.0.242 66.103.230.30 4974
80 - - - - - - - - -
2008-12-02 11:45:25 OPEN TCP 10.1.0.242 66.103.230.30 4975
80 - - - - - - - - -
2008-12-02 11:45:25 CLOSE TCP 10.1.0.242 66.103.230.30 4975
80 - - - - - - - - -
2008-12-02 11:45:25 OPEN TCP 10.1.0.242 66.103.230.30 4976
80 - - - - - - - - -
2008-12-02 11:45:25 CLOSE TCP 10.1.0.242 66.103.230.30 4976
80 - - - - - - - - -
2008-12-02 11:45:25 OPEN TCP 10.1.0.242 66.103.230.30 4977
80 - - - - - - - - -
2008-12-02 11:45:25 CLOSE TCP 10.1.0.242 66.103.230.30 4977
80 - - - - - - - - -
2008-12-02 11:45:25 CLOSE TCP 10.1.0.242 66.103.230.30 4970
80 - - - - - - - - -
2008-12-02 11:45:25 OPEN TCP 10.1.0.242 66.103.230.30 4978
80 - - - - - - - - -
2008-12-02 11:45:25 OPEN TCP 10.1.0.242 66.103.230.30 4979
80 - - - - - - - - -
2008-12-02 11:45:25 CLOSE TCP 10.1.0.242 66.103.230.30 4978
80 - - - - - - - - -
2008-12-02 11:45:25 OPEN TCP 10.1.0.242 66.103.230.30 4980
80 - - - - - - - - -
2008-12-02 11:45:25 CLOSE TCP 10.1.0.242 66.103.230.30 4979
80 - - - - - - - - -
2008-12-02 11:28:03 DROP TCP 66.103.230.30 10.1.0.242 80 4290 48 SA
2315198760 2359628516 5840 - - - RECEIVE
2008-12-02 11:28:03 DROP TCP 66.103.230.30 10.1.0.242 80 4291 48 SA
2305186690 3243992885 5840 - - - RECEIVE
2008-12-02 11:28:03 DROP TCP 66.103.230.30 10.1.0.242 80 4292 48 SA
2304886328 703770454 5840 - - - RECEIVE
2008-12-02 11:28:03 DROP TCP 66.103.230.30 10.1.0.242 80 4293 48 SA
2309407895 4066596432 5840 - - - RECEIVE
2008-12-02 11:28:03 DROP TCP 66.103.230.30 10.1.0.242 80 4294 48 SA
2305199731 800921536 5840 - - - RECEIVE
2008-12-02 11:28:03 DROP TCP 66.103.230.30 10.1.0.242 80 4295 48 SA
2309455607 1972462813 5840 - - - RECEIVE
2008-12-02 11:28:03 DROP TCP 66.103.230.30 10.1.0.242 80 4296 48 SA
2308523674 3789496453 5840 - - - RECEIVE
2008-12-02 11:28:03 DROP TCP 66.103.230.30 10.1.0.242 80 4297 48 SA
2310517848 2091849474 5840 - - - RECEIVE
2008-12-02 11:28:03 DROP TCP 66.103.230.30 10.1.0.242 80 4298 48 SA
2317522088 3012446622 5840 - - - RECEIVE
In this case a lingering NAT entry was created for each drop packet. Here
is what ends up in the NATLOG file. These connections will stay until the
time out is reached. A total of 81 connections where made with this attempt.
2. 10.1.0.242 | 1808 | 55428 | 66.103.230.30 |
80| 10| 101
3. 10.1.0.242 | 1800 | 55420 | 66.103.230.30 |
80| 10| 154
4. 10.1.0.242 | 1799 | 55419 | 66.103.230.30 |
80| 10| 154
5. 10.1.0.242 | 1798 | 55418 | 66.103.230.30 |
80| 10| 154
6. 10.1.0.242 | 1797 | 55417 | 66.103.230.30 |
80| 10| 155
7. 10.1.0.242 | 1796 | 55416 | 66.103.230.30 |
80| 10| 155
8. 10.1.0.242 | 1795 | 55415 | 66.103.230.30 |
80| 10| 155
9. 10.1.0.242 | 1794 | 55414 | 66.103.230.30 |
80| 10| 155
10. 10.1.0.242 | 1793 | 55413 | 66.103.230.30 |
80| 10| 155
A number of our XP machines are doing this, and that is what was filling the
NAT table. I have virus scanned, and checked them for spy etc, and found
nothing abnormal.
I will post what ever results I can find.
Thanks again for the help.
Jim
"Jim Burghart" <pumpkinj@nycap.rr.com> wrote in message
news:HonXk.3308$wo4.762@kovat.provo.novell.com...
>I have a strange issue with a Bordermanager server. It is 3.9SP1 on a NW
>6.5sp7 server. After the server has been running it stops passing traffic
>to the Internet. I checked the NAT table and it has 5000 entries (the max I
>believe) The entries are old, so it looks like it is not refreshing the
>table.
>
> If I disable NAT on the public interafce, then enable it things start
> moving again.
>
> Any ideas?
>
> Thanks,
>
> Jim
>