Using PortQryV2 I got the result that on a remote server port (1434) is
FILTERED.
What could be the cause?
How can I change its state to LISTENING?

Thanks, Dan

Port filtering in Windows 2000 is done in Control
Panel|Network|"connection"|Properties|Tcp/Ip|Properties|Advanced|Options|Tcp/Ip
Filtering|Properties

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"dan" wrote:
| Using PortQryV2 I got the result that on a remote server port (1434) is
| FILTERED.
| What could be the cause?
| How can I change its state to LISTENING?
|
| Thanks, Dan
|
|
|
|

Thanks Dave.
Sorry, I didn't mention that the server is Windows 2003. There is no
"Network" applet in the Control Panel.
Thanks again,
Dan



"Dave Patrick" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> Port filtering in Windows 2000 is done in Control
> Panel|Network|"connection"|Properties|Tcp/Ip|Properties|Advanced|Options|Tcp/Ip
> Filtering|Properties
>
> --
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "dan" wrote:
> | Using PortQryV2 I got the result that on a remote server port (1434) is
> | FILTERED.
> | What could be the cause?
> | How can I change its state to LISTENING?
> |
> | Thanks, Dan
> |
> |
> |
> |
>
>

The icon should be there. Either case try from a command prompt;

control.exe %windir%\system32\ncpa.cpl, network

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"dan" wrote:
| Thanks Dave.
| Sorry, I didn't mention that the server is Windows 2003. There is no
| "Network" applet in the Control Panel.
| Thanks again,
| Dan

Dave,
Many thanks for your hint.
I managed to access the TCP/IP Filtering tab, where "Enable TCP/IP
Filtering" is not checked.
I assume that Filtering is disabled.
Then how is it possible for MS Port Query to report that Port 1433 is
FILTERED?
On a second server with the same settings (designed to mirror the first one)
Port Query reports that Port 1433 is NOT LISTENING.
On both servers we have a SQL Server instance set up to listen on port 1433.

My thanks again,
Dan



"Dave Patrick" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> The icon should be there. Either case try from a command prompt;
>
> control.exe %windir%\system32\ncpa.cpl, network
>
> --
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "dan" wrote:
> | Thanks Dave.
> | Sorry, I didn't mention that the server is Windows 2003. There is no
> | "Network" applet in the Control Panel.
> | Thanks again,
> | Dan
>
>

This may help.

LISTENING This response indicates that a process is listening on the target
port. PortQry received a response from the target port.

NOT LISTENING This response indicates that no process is listening on the
target port. PortQry received one of the following Internet Control Message
Protocol (ICMP) messages from the target port:
Destination unreachable
Port unreachable

FILTERED This response indicates that the target port is being filtered.
PortQry did not receive a response from the target port. A process may or
may not be listening on the target port. By default, PortQry queries a TCP
port three times before it returns a response of FILTERED and queries a UDP
port one time before it returns a response of FILTERED.

http://support.microsoft.com/kb/832919

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"dan" wrote:
| Dave,
| Many thanks for your hint.
| I managed to access the TCP/IP Filtering tab, where "Enable TCP/IP
| Filtering" is not checked.
| I assume that Filtering is disabled.
| Then how is it possible for MS Port Query to report that Port 1433 is
| FILTERED?
| On a second server with the same settings (designed to mirror the first
one)
| Port Query reports that Port 1433 is NOT LISTENING.
| On both servers we have a SQL Server instance set up to listen on port
1433.
|
| My thanks again,
| Dan

Many thanks Dave.
Using the -local parameter on computer 1 I got the followng result which
looks good
===================================================================================
Process ID: 1124


Service Name: MSSQL$EL3E1 <============this is the correct SQL Server
instance
Display Name: MSSQL$EL3E1
Service Type: runs in its own process



PID Port Local IP State Remote IP:Port
1124 TCP 1433 0.0.0.0 LISTENING 0.0.0.0:2208
1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:2382
1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:2397
1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:4800
1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:4845
1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:4854
1124 UDP 1434 0.0.0.0 *:*

==============================================================================================



Making a query from computer 2 to computer 1:

=============================================================================================

Querying target system called:


<IPaddress1>


Attempting to resolve IP address to a name...


IP address resolved to <correct computer name>


querying...


TCP port 1433 (ms-sql-s service): FILTERED

===============================================================================================



Taking into consideration that the LAN has TCP filtering disabled, who else
might be the culprit?



Thank you very much,

Dan








"Dave Patrick" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> This may help.
>
> LISTENING This response indicates that a process is listening on the
> target
> port. PortQry received a response from the target port.
>
> NOT LISTENING This response indicates that no process is listening on the
> target port. PortQry received one of the following Internet Control
> Message
> Protocol (ICMP) messages from the target port:
> Destination unreachable
> Port unreachable
>
> FILTERED This response indicates that the target port is being filtered.
> PortQry did not receive a response from the target port. A process may or
> may not be listening on the target port. By default, PortQry queries a TCP
> port three times before it returns a response of FILTERED and queries a
> UDP
> port one time before it returns a response of FILTERED.
>
> http://support.microsoft.com/kb/832919
>
> --
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "dan" wrote:
> | Dave,
> | Many thanks for your hint.
> | I managed to access the TCP/IP Filtering tab, where "Enable TCP/IP
> | Filtering" is not checked.
> | I assume that Filtering is disabled.
> | Then how is it possible for MS Port Query to report that Port 1433 is
> | FILTERED?
> | On a second server with the same settings (designed to mirror the first
> one)
> | Port Query reports that Port 1433 is NOT LISTENING.
> | On both servers we have a SQL Server instance set up to listen on port
> 1433.
> |
> | My thanks again,
> | Dan
>
>

These may help.

http://support.microsoft.com/?id=813878
http://support.microsoft.com/?id=823938
http://www.microsoft.com/windows2000...ipsecpol-o.asp
http://support.microsoft.com/kb/814130

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"dan" wrote:
| Many thanks Dave.
| Using the -local parameter on computer 1 I got the followng result which
| looks good
|
===================================================================================
| Process ID: 1124
|
|
| Service Name: MSSQL$EL3E1 <============this is the correct SQL Server
| instance
| Display Name: MSSQL$EL3E1
| Service Type: runs in its own process
|
|
|
| PID Port Local IP State Remote IP:Port
| 1124 TCP 1433 0.0.0.0 LISTENING 0.0.0.0:2208
| 1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:2382
| 1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:2397
| 1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:4800
| 1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:4845
| 1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:4854
| 1124 UDP 1434 0.0.0.0 *:*
|
|
==============================================================================================
|
|
|
| Making a query from computer 2 to computer 1:
|
|
=============================================================================================
|
| Querying target system called:
|
|
| <IPaddress1>
|
|
| Attempting to resolve IP address to a name...
|
|
| IP address resolved to <correct computer name>
|
|
| querying...
|
|
| TCP port 1433 (ms-sql-s service): FILTERED
|
|
===============================================================================================
|
|
|
| Taking into consideration that the LAN has TCP filtering disabled, who
else
| might be the culprit?
|
|
|
| Thank you very much,
|
| Dan

Interesting stuff! I'll start reading right away.
Thanks Dave, Dan



"Dave Patrick" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> These may help.
>
> http://support.microsoft.com/?id=813878
> http://support.microsoft.com/?id=823938
> http://www.microsoft.com/windows2000...ipsecpol-o.asp
> http://support.microsoft.com/kb/814130
>
> --
> Regards,
>
> Dave Patrick ....Please no email replies - reply in newsgroup.
> Microsoft Certified Professional
> Microsoft MVP [Windows]
> http://www.microsoft.com/protect
>
> "dan" wrote:
> | Many thanks Dave.
> | Using the -local parameter on computer 1 I got the followng result which
> | looks good
> |
> ===================================================================================
> | Process ID: 1124
> |
> |
> | Service Name: MSSQL$EL3E1 <============this is the correct SQL
> Server
> | instance
> | Display Name: MSSQL$EL3E1
> | Service Type: runs in its own process
> |
> |
> |
> | PID Port Local IP State Remote IP:Port
> | 1124 TCP 1433 0.0.0.0 LISTENING 0.0.0.0:2208
> | 1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:2382
> | 1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:2397
> | 1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:4800
> | 1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:4845
> | 1124 TCP 1433 <IPaddress1> ESTABLISHED <IPaddress1>:4854
> | 1124 UDP 1434 0.0.0.0 *:*
> |
> |
> ==============================================================================================
> |
> |
> |
> | Making a query from computer 2 to computer 1:
> |
> |
> =============================================================================================
> |
> | Querying target system called:
> |
> |
> | <IPaddress1>
> |
> |
> | Attempting to resolve IP address to a name...
> |
> |
> | IP address resolved to <correct computer name>
> |
> |
> | querying...
> |
> |
> | TCP port 1433 (ms-sql-s service): FILTERED
> |
> |
> ===============================================================================================
> |
> |
> |
> | Taking into consideration that the LAN has TCP filtering disabled, who
> else
> | might be the culprit?
> |
> |
> |
> | Thank you very much,
> |
> | Dan
>
>

You're welcome.

--
Regards,

Dave Patrick ....Please no email replies - reply in newsgroup.
Microsoft Certified Professional
Microsoft MVP [Windows]
http://www.microsoft.com/protect

"dan" wrote:
|
| Interesting stuff! I'll start reading right away.
| Thanks Dave, Dan