Re: TCP/IP Filtering
From: dave (dave@netmedic.net)
Date: 10/22/02
- Next message: Daniel Angelucci: "Re: Windows 2000 VPN and/or SSL"
- Previous message: John Hardin: "hotfixes"
- In reply to: Matt Prall: "Re: TCP/IP Filtering"
- Next in thread: Karl Levinson [x y] MVP: "Re: TCP/IP Filtering"
- Reply: Karl Levinson [x y] MVP: "Re: TCP/IP Filtering"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
From: "dave" <dave@netmedic.net> Date: Mon, 21 Oct 2002 19:09:49 -0700
Matt,
Thanks, but i want to use the OS and see what we can
accomplish.
Dave
>-----Original Message-----
>I would recommend you get a *real* software firewall,
what you are
>wanting to do is much easier in other products such as
norton personal
>firewall etc.
>
>dave kleiman wrote:
>> I have discovered (not sure if that is the right word)
an
>> interesting thing in reference to using TCP/IP
Filtering
>> on a W2000 client.
>>
>> I was attempting to setup my home system using the
built
>> in TCP/IP Filtering. I Allowed only Ports 25 Mail, 53
>> DNS, 67&68 DHCP, and 80&443 Internet.
>>
>> Well I found out that DNS returns to a client on a port
>>
>>>1024. So I picked the first 3 unassigned above 1024
>>
>> ports. Well that worked until the third time I opened
a
>> web browser (no DNS resolution). I looked with NETSTAT -
na
>> and found that it was now trying to use a port higher
than
>> the 3 I selected. I opened up 10 more >1024 ports.
Well
>> the worked till about the 7th time I opened the web
>> browser.
>>
>> I checked again it was now trying to use higher ports.
>> Well I continued this watching NETSTAT show that each
>> subsequent DNS request went up the above >1024 ladder.
>> The thing I could not figure out was how to
reset/release
>> the previously used ports.
>>
>> I waited for 24 hours, thinking it was a timeout issue,
>> and tried again it went up to the next port (not used
yet)
>>
>>>1024. I tried disabling and re-enabling the Interface,
>>
>> ipconfig /renew and /flushdns but it still new to go up
>> past the last >1024 port used.
>>
>> Rebooting the machine was the only way to start over.
Of
>> course examining again yielded the same results.
>>
>> Do you know a way to flush out the system to release or
>> reuse those same ports without rebooting?
>>
>> Thanks,
>>
>> Dave
>
>.
>
- Next message: Daniel Angelucci: "Re: Windows 2000 VPN and/or SSL"
- Previous message: John Hardin: "hotfixes"
- In reply to: Matt Prall: "Re: TCP/IP Filtering"
- Next in thread: Karl Levinson [x y] MVP: "Re: TCP/IP Filtering"
- Reply: Karl Levinson [x y] MVP: "Re: TCP/IP Filtering"
- Messages sorted by: [ date ] [ thread ] [ subject ] [ author ] [ attachment ]
Relevant Pages
|