Re: Event ID 1054 and ip filter

From: Charles Elliott (elliott.ct_at_verizon.net)
Date: 04/01/04 

Date: Thu, 1 Apr 2004 13:16:13 -0500

Thanks for the information on how you solved the problem, but you raise
another question: Are you using the firewall built-in to the Windows
product you are using? The reason I ask is because the "Internet Connection
Firewall" that comes with Server 2003 does not seem to accept any notation
for "From Any Port," to use your terms. I had to stop using it because a
request for DNS or any service can come from any port on a computer on the
LAN. I wound up using the firewall built-in to my router.

"Molly King" <anonymous@discussions.microsoft.com> wrote in message
news:1B7CE6DC-5F75-4C1D-B36C-EF51AC8CB64B@microsoft.com...
> Thanks for the sugguestion. This is what I did to fix it. My original ip
filter rules were set up as follows: From source <the test subnet> to
Destination <My ip address> 'permit' protocol <TCP> From Any Port To this
port <53>. I did this for all the ports I listed in the original question.
Everything started working fine when I added rules as followed: From source
<My ip address> to Destination <the test subnet> 'permit' protocol <TCP>
>From Any port To this port <53>. I did this for ports 53 tcp and udp, 389
tcp, 139 tcp and 445 tcp. Since all the original rules (and the new ones)
are 'mirrored,' I guess I don't understand what Mirrored means.

Relevant Pages

  • Re: Windows 2000 - MS Access XP and Sql Server 2005.
    ... The library is the library for the named pipes protocol; ... adding tcp: before the name of the server. ... the right port to use) at the end. ... I can't connect a client computer with windows 2000 to sql server 2005: ...
    (microsoft.public.access.adp.sqlserver)
  • Re: Ports other than 53 required for proper DNS operation????
    ... DNS should be straight TCP/IP on port 53, ... UDP first, then TCP. ... With Windows communication within a network, or even on the local server, ...
    (microsoft.public.windows.server.dns)
  • Re: Still Cant Block 135 with Symantec Firewall 2.01.
    ... >when I run the security checks it still says Port 135 is Open. ... Port 135 is used by Windows NT, itself as part of your network system. ... Exchange Administrator (MS Exchange Server version 5.0) ...
    (comp.security.firewalls)
  • Re: Firewall Log Entries Help
    ... TCP 139 is used for Windows File Sharing ... TCP 445 is used when NetBIOS over TCP/IP is enabled. ... TCP 135 port used by Outlook to contact an Exchange Server ... My ethernet card have stop to responds to internet connections since this ...
    (microsoft.public.windows.server.networking)
  • Re: excessive TCP dulplicate acks revisted
    ... The tcp duplicate ACK attack is back. ... there was a thread on duplicate TCP acks in -CURRENT. ... TCP STREAM TEST from localhost port 0 AF_INET to greenhouse- george.18clay.com port 0 AF_INET ... Socket Socket Message Elapsed ...
    (freebsd-current)