Home Network w/ 2 SQLServers: 1-way problem

I have a WinXP Pro home network which is behind a firewall. Within
this network I have 2 computers running SQLServer 2000: my desktop and
my laptop. Both instances are configured identically and use Windows
authentication. I use Enterprise Manager.
- My laptop can "see" the desktop's instance; i.e., I'm able to create
a SQLServer Registration entry and browse the desktop's databases
- My desktop can NOT "see" the laptop's instance. When I try to create
a SQLServer Registration, I receive "SQL Server does not exist or
access denied..."
I've tried registering via the laptop's computer name, and I've tried
registering via the laptop's local IP address.
My firewall is not allowing access to port 1433 for either computer.
Both computers can see each other through file/printer sharing.
SQLServer seems to be the only case where there is a "blockage".
Any help is appreciated...
-JeffOne other note -- both machines can ping each other by IP and by name.
Jeff wrote:
> I have a WinXP Pro home network which is behind a firewall. Within
> this network I have 2 computers running SQLServer 2000: my desktop
and
> my laptop. Both instances are configured identically and use Windows
> authentication. I use Enterprise Manager.
> - My laptop can "see" the desktop's instance; i.e., I'm able to
create
> a SQLServer Registration entry and browse the desktop's databases
> - My desktop can NOT "see" the laptop's instance. When I try to
create
> a SQLServer Registration, I receive "SQL Server does not exist or
> access denied..."
> I've tried registering via the laptop's computer name, and I've tried
> registering via the laptop's local IP address.
> My firewall is not allowing access to port 1433 for either computer.
> Both computers can see each other through file/printer sharing.
> SQLServer seems to be the only case where there is a "blockage".
> Any help is appreciated...
> -Jeff|||Jeff wrote:
> I have a WinXP Pro home network which is behind a firewall. Within
> this network I have 2 computers running SQLServer 2000: my desktop
> and my laptop. Both instances are configured identically and use
> Windows authentication. I use Enterprise Manager.
>
If you're blocking 1433 on both PCs, how are you connecting to the
desktop from the laptop? Named Pipes? Try using the same network
protocol to connect the other way around.
David Gugick
Imceda Software
www.imceda.com|||Would the firewall blockage apply internally? I thought the firewall
would only prevent outside access? In other words, I didn't think that
my firewall would prevent internal machines from communicating?
Anyhow, both Named Pipes and TCP/IP are enabled.
The Server Network Utility and Client Network Utility settings are
identical on both machines.

> If you're blocking 1433 on both PCs, how are you connecting to the
> desktop from the laptop? Named Pipes? Try using the same network
> protocol to connect the other way around.
> --
> David Gugick
> Imceda Software
> www.imceda.com|||Jeff wrote:
> Would the firewall blockage apply internally? I thought the firewall
> would only prevent outside access? In other words, I didn't think
> that my firewall would prevent internal machines from communicating?
> Anyhow, both Named Pipes and TCP/IP are enabled.
> The Server Network Utility and Client Network Utility settings are
> identical on both machines.
Turn off any firewalls and see what happens.
David Gugick
Imceda Software
www.imceda.com|||Is your Firewall also acting as your LAN router? If so, it is probably
blocking your internal traffic as well. Consider putting your Firewall in
front of a real LAN router, that's how it is usually configured. If so,
then that configuration would behave as you suspect, blocking only traffic
onto/out of the router, but not packets routed between back end hosts.
Sincerely,
Anthony Thomas
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:%23mN$uleHFHA.3196@.TK2MSFTNGP15.phx.gbl...
Jeff wrote:
> Would the firewall blockage apply internally? I thought the firewall
> would only prevent outside access? In other words, I didn't think
> that my firewall would prevent internal machines from communicating?
> Anyhow, both Named Pipes and TCP/IP are enabled.
> The Server Network Utility and Client Network Utility settings are
> identical on both machines.
Turn off any firewalls and see what happens.
David Gugick
Imceda Software
www.imceda.comsql

Home Network w/ 2 SQLServers: 1-way problem

I have a WinXP Pro home network which is behind a firewall. Within
this network I have 2 computers running SQLServer 2000: my desktop and
my laptop. Both instances are configured identically and use Windows
authentication. I use Enterprise Manager.
- My laptop can "see" the desktop's instance; i.e., I'm able to create
a SQLServer Registration entry and browse the desktop's databases
- My desktop can NOT "see" the laptop's instance. When I try to create
a SQLServer Registration, I receive "SQL Server does not exist or
access denied..."
I've tried registering via the laptop's computer name, and I've tried
registering via the laptop's local IP address.
My firewall is not allowing access to port 1433 for either computer.
Both computers can see each other through file/printer sharing.
SQLServer seems to be the only case where there is a "blockage".
Any help is appreciated...
-Jeff
One other note -- both machines can ping each other by IP and by name.
Jeff wrote:
> I have a WinXP Pro home network which is behind a firewall. Within
> this network I have 2 computers running SQLServer 2000: my desktop
and
> my laptop. Both instances are configured identically and use Windows
> authentication. I use Enterprise Manager.
> - My laptop can "see" the desktop's instance; i.e., I'm able to
create
> a SQLServer Registration entry and browse the desktop's databases
> - My desktop can NOT "see" the laptop's instance. When I try to
create
> a SQLServer Registration, I receive "SQL Server does not exist or
> access denied..."
> I've tried registering via the laptop's computer name, and I've tried
> registering via the laptop's local IP address.
> My firewall is not allowing access to port 1433 for either computer.
> Both computers can see each other through file/printer sharing.
> SQLServer seems to be the only case where there is a "blockage".
> Any help is appreciated...
> -Jeff
|||Jeff wrote:
> I have a WinXP Pro home network which is behind a firewall. Within
> this network I have 2 computers running SQLServer 2000: my desktop
> and my laptop. Both instances are configured identically and use
> Windows authentication. I use Enterprise Manager.
>
If you're blocking 1433 on both PCs, how are you connecting to the
desktop from the laptop? Named Pipes? Try using the same network
protocol to connect the other way around.
David Gugick
Imceda Software
www.imceda.com
|||Would the firewall blockage apply internally? I thought the firewall
would only prevent outside access? In other words, I didn't think that
my firewall would prevent internal machines from communicating?
Anyhow, both Named Pipes and TCP/IP are enabled.
The Server Network Utility and Client Network Utility settings are
identical on both machines.

> If you're blocking 1433 on both PCs, how are you connecting to the
> desktop from the laptop? Named Pipes? Try using the same network
> protocol to connect the other way around.
> --
> David Gugick
> Imceda Software
> www.imceda.com
|||Jeff wrote:
> Would the firewall blockage apply internally? I thought the firewall
> would only prevent outside access? In other words, I didn't think
> that my firewall would prevent internal machines from communicating?
> Anyhow, both Named Pipes and TCP/IP are enabled.
> The Server Network Utility and Client Network Utility settings are
> identical on both machines.
Turn off any firewalls and see what happens.
David Gugick
Imceda Software
www.imceda.com
|||Is your Firewall also acting as your LAN router? If so, it is probably
blocking your internal traffic as well. Consider putting your Firewall in
front of a real LAN router, that's how it is usually configured. If so,
then that configuration would behave as you suspect, blocking only traffic
onto/out of the router, but not packets routed between back end hosts.
Sincerely,
Anthony Thomas

"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:%23mN$uleHFHA.3196@.TK2MSFTNGP15.phx.gbl...
Jeff wrote:
> Would the firewall blockage apply internally? I thought the firewall
> would only prevent outside access? In other words, I didn't think
> that my firewall would prevent internal machines from communicating?
> Anyhow, both Named Pipes and TCP/IP are enabled.
> The Server Network Utility and Client Network Utility settings are
> identical on both machines.
Turn off any firewalls and see what happens.
David Gugick
Imceda Software
www.imceda.com

Home Network w/ 2 SQLServers: 1-way problem

I have a WinXP Pro home network which is behind a firewall. Within
this network I have 2 computers running SQLServer 2000: my desktop and
my laptop. Both instances are configured identically and use Windows
authentication. I use Enterprise Manager.
- My laptop can "see" the desktop's instance; i.e., I'm able to create
a SQLServer Registration entry and browse the desktop's databases
- My desktop can NOT "see" the laptop's instance. When I try to create
a SQLServer Registration, I receive "SQL Server does not exist or
access denied..."
I've tried registering via the laptop's computer name, and I've tried
registering via the laptop's local IP address.
My firewall is not allowing access to port 1433 for either computer.
Both computers can see each other through file/printer sharing.
SQLServer seems to be the only case where there is a "blockage".
Any help is appreciated...
-JeffOne other note -- both machines can ping each other by IP and by name.
Jeff wrote:
> I have a WinXP Pro home network which is behind a firewall. Within
> this network I have 2 computers running SQLServer 2000: my desktop
and
> my laptop. Both instances are configured identically and use Windows
> authentication. I use Enterprise Manager.
> - My laptop can "see" the desktop's instance; i.e., I'm able to
create
> a SQLServer Registration entry and browse the desktop's databases
> - My desktop can NOT "see" the laptop's instance. When I try to
create
> a SQLServer Registration, I receive "SQL Server does not exist or
> access denied..."
> I've tried registering via the laptop's computer name, and I've tried
> registering via the laptop's local IP address.
> My firewall is not allowing access to port 1433 for either computer.
> Both computers can see each other through file/printer sharing.
> SQLServer seems to be the only case where there is a "blockage".
> Any help is appreciated...
> -Jeff|||Jeff wrote:
> I have a WinXP Pro home network which is behind a firewall. Within
> this network I have 2 computers running SQLServer 2000: my desktop
> and my laptop. Both instances are configured identically and use
> Windows authentication. I use Enterprise Manager.
>
If you're blocking 1433 on both PCs, how are you connecting to the
desktop from the laptop? Named Pipes? Try using the same network
protocol to connect the other way around.
--
David Gugick
Imceda Software
www.imceda.com|||Would the firewall blockage apply internally? I thought the firewall
would only prevent outside access? In other words, I didn't think that
my firewall would prevent internal machines from communicating?
Anyhow, both Named Pipes and TCP/IP are enabled.
The Server Network Utility and Client Network Utility settings are
identical on both machines.
> If you're blocking 1433 on both PCs, how are you connecting to the
> desktop from the laptop? Named Pipes? Try using the same network
> protocol to connect the other way around.
> --
> David Gugick
> Imceda Software
> www.imceda.com|||Jeff wrote:
> Would the firewall blockage apply internally? I thought the firewall
> would only prevent outside access? In other words, I didn't think
> that my firewall would prevent internal machines from communicating?
> Anyhow, both Named Pipes and TCP/IP are enabled.
> The Server Network Utility and Client Network Utility settings are
> identical on both machines.
Turn off any firewalls and see what happens.
--
David Gugick
Imceda Software
www.imceda.com|||Is your Firewall also acting as your LAN router? If so, it is probably
blocking your internal traffic as well. Consider putting your Firewall in
front of a real LAN router, that's how it is usually configured. If so,
then that configuration would behave as you suspect, blocking only traffic
onto/out of the router, but not packets routed between back end hosts.
Sincerely,
Anthony Thomas
"David Gugick" <davidg-nospam@.imceda.com> wrote in message
news:%23mN$uleHFHA.3196@.TK2MSFTNGP15.phx.gbl...
Jeff wrote:
> Would the firewall blockage apply internally? I thought the firewall
> would only prevent outside access? In other words, I didn't think
> that my firewall would prevent internal machines from communicating?
> Anyhow, both Named Pipes and TCP/IP are enabled.
> The Server Network Utility and Client Network Utility settings are
> identical on both machines.
Turn off any firewalls and see what happens.
--
David Gugick
Imceda Software
www.imceda.com

High Volume of Net Traffic coming from MSSQL

We're having a bit of an issue with network traffic being generated from one
of our MSSQL Servers.
It seems that when we launch Enterprise Manager on a remote computer
(usually at another office), the MSSQL servers start sending packets to the
EM regardless of whether we are maintaining an active connection to the
server or not. What is happening is that these packets are being lost and
reported in our firewall as 'host unreachable'. These packets are also
firing every second for each EM open across our network, so this is becoming
a bit of a pain for our poor network guys. The other odd thing is that the
firewall is only reporting one-way traffic, from the server to the client,
but the client is not sending any traffic back down unless it is actively
connected to the remote server.
Any thoughts as to why this might be happening, or better yet, a way to cull
this traffic?
We're running MSSQL 2000 SP3a on Windows 2003 servers.
Thanks in advance!
Mike,Have you applied the post-SP3a hotfix?
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
We're having a bit of an issue with network traffic being generated from one
of our MSSQL Servers.
It seems that when we launch Enterprise Manager on a remote computer
(usually at another office), the MSSQL servers start sending packets to the
EM regardless of whether we are maintaining an active connection to the
server or not. What is happening is that these packets are being lost and
reported in our firewall as 'host unreachable'. These packets are also
firing every second for each EM open across our network, so this is becoming
a bit of a pain for our poor network guys. The other odd thing is that the
firewall is only reporting one-way traffic, from the server to the client,
but the client is not sending any traffic back down unless it is actively
connected to the remote server.
Any thoughts as to why this might be happening, or better yet, a way to cull
this traffic?
We're running MSSQL 2000 SP3a on Windows 2003 servers.
Thanks in advance!
Mike,|||We have the entire SP3a hotfix installed, but I am unaware of a post SP3a fix
- are you referring to SP4?
"Tom Moreau" wrote:
> Have you applied the post-SP3a hotfix?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
> news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
> We're having a bit of an issue with network traffic being generated from one
> of our MSSQL Servers.
> It seems that when we launch Enterprise Manager on a remote computer
> (usually at another office), the MSSQL servers start sending packets to the
> EM regardless of whether we are maintaining an active connection to the
> server or not. What is happening is that these packets are being lost and
> reported in our firewall as 'host unreachable'. These packets are also
> firing every second for each EM open across our network, so this is becoming
> a bit of a pain for our poor network guys. The other odd thing is that the
> firewall is only reporting one-way traffic, from the server to the client,
> but the client is not sending any traffic back down unless it is actively
> connected to the remote server.
> Any thoughts as to why this might be happening, or better yet, a way to cull
> this traffic?
> We're running MSSQL 2000 SP3a on Windows 2003 servers.
> Thanks in advance!
> Mike,
>|||Define "entire SP3a hotfix". There is the service pack - SP3a - and then
there is the hotfix. Are you saying that you have applied SP3a but not the
hotfix? IOW, have you applied:
http://support.microsoft.com/kb/821277
--
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
news:5D90B16F-7EDB-401C-8022-106365D44347@.microsoft.com...
We have the entire SP3a hotfix installed, but I am unaware of a post SP3a
fix
- are you referring to SP4?
"Tom Moreau" wrote:
> Have you applied the post-SP3a hotfix?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
> news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
> We're having a bit of an issue with network traffic being generated from
> one
> of our MSSQL Servers.
> It seems that when we launch Enterprise Manager on a remote computer
> (usually at another office), the MSSQL servers start sending packets to
> the
> EM regardless of whether we are maintaining an active connection to the
> server or not. What is happening is that these packets are being lost and
> reported in our firewall as 'host unreachable'. These packets are also
> firing every second for each EM open across our network, so this is
> becoming
> a bit of a pain for our poor network guys. The other odd thing is that
> the
> firewall is only reporting one-way traffic, from the server to the client,
> but the client is not sending any traffic back down unless it is actively
> connected to the remote server.
> Any thoughts as to why this might be happening, or better yet, a way to
> cull
> this traffic?
> We're running MSSQL 2000 SP3a on Windows 2003 servers.
> Thanks in advance!
> Mike,
>

High Volume of Net Traffic coming from MSSQL

We're having a bit of an issue with network traffic being generated from one
of our MSSQL Servers.
It seems that when we launch Enterprise Manager on a remote computer
(usually at another office), the MSSQL servers start sending packets to the
EM regardless of whether we are maintaining an active connection to the
server or not. What is happening is that these packets are being lost and
reported in our firewall as 'host unreachable'. These packets are also
firing every second for each EM open across our network, so this is becoming
a bit of a pain for our poor network guys. The other odd thing is that the
firewall is only reporting one-way traffic, from the server to the client,
but the client is not sending any traffic back down unless it is actively
connected to the remote server.
Any thoughts as to why this might be happening, or better yet, a way to cull
this traffic?
We're running MSSQL 2000 SP3a on Windows 2003 servers.
Thanks in advance!
Mike,Have you applied the post-SP3a hotfix?
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
We're having a bit of an issue with network traffic being generated from one
of our MSSQL Servers.
It seems that when we launch Enterprise Manager on a remote computer
(usually at another office), the MSSQL servers start sending packets to the
EM regardless of whether we are maintaining an active connection to the
server or not. What is happening is that these packets are being lost and
reported in our firewall as 'host unreachable'. These packets are also
firing every second for each EM open across our network, so this is becoming
a bit of a pain for our poor network guys. The other odd thing is that the
firewall is only reporting one-way traffic, from the server to the client,
but the client is not sending any traffic back down unless it is actively
connected to the remote server.
Any thoughts as to why this might be happening, or better yet, a way to cull
this traffic?
We're running MSSQL 2000 SP3a on Windows 2003 servers.
Thanks in advance!
Mike,|||We have the entire SP3a hotfix installed, but I am unaware of a post SP3a fi
x
- are you referring to SP4?
"Tom Moreau" wrote:

> Have you applied the post-SP3a hotfix?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
> news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
> We're having a bit of an issue with network traffic being generated from o
ne
> of our MSSQL Servers.
> It seems that when we launch Enterprise Manager on a remote computer
> (usually at another office), the MSSQL servers start sending packets to th
e
> EM regardless of whether we are maintaining an active connection to the
> server or not. What is happening is that these packets are being lost and
> reported in our firewall as 'host unreachable'. These packets are also
> firing every second for each EM open across our network, so this is becomi
ng
> a bit of a pain for our poor network guys. The other odd thing is that th
e
> firewall is only reporting one-way traffic, from the server to the client,
> but the client is not sending any traffic back down unless it is actively
> connected to the remote server.
> Any thoughts as to why this might be happening, or better yet, a way to cu
ll
> this traffic?
> We're running MSSQL 2000 SP3a on Windows 2003 servers.
> Thanks in advance!
> Mike,
>|||Define "entire SP3a hotfix". There is the service pack - SP3a - and then
there is the hotfix. Are you saying that you have applied SP3a but not the
hotfix? IOW, have you applied:
http://support.microsoft.com/kb/821277
Tom
----
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
.
"Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
news:5D90B16F-7EDB-401C-8022-106365D44347@.microsoft.com...
We have the entire SP3a hotfix installed, but I am unaware of a post SP3a
fix
- are you referring to SP4?
"Tom Moreau" wrote:

> Have you applied the post-SP3a hotfix?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
> news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
> We're having a bit of an issue with network traffic being generated from
> one
> of our MSSQL Servers.
> It seems that when we launch Enterprise Manager on a remote computer
> (usually at another office), the MSSQL servers start sending packets to
> the
> EM regardless of whether we are maintaining an active connection to the
> server or not. What is happening is that these packets are being lost and
> reported in our firewall as 'host unreachable'. These packets are also
> firing every second for each EM open across our network, so this is
> becoming
> a bit of a pain for our poor network guys. The other odd thing is that
> the
> firewall is only reporting one-way traffic, from the server to the client,
> but the client is not sending any traffic back down unless it is actively
> connected to the remote server.
> Any thoughts as to why this might be happening, or better yet, a way to
> cull
> this traffic?
> We're running MSSQL 2000 SP3a on Windows 2003 servers.
> Thanks in advance!
> Mike,
>

High Volume of Net Traffic coming from MSSQL

We're having a bit of an issue with network traffic being generated from one
of our MSSQL Servers.
It seems that when we launch Enterprise Manager on a remote computer
(usually at another office), the MSSQL servers start sending packets to the
EM regardless of whether we are maintaining an active connection to the
server or not. What is happening is that these packets are being lost and
reported in our firewall as 'host unreachable'. These packets are also
firing every second for each EM open across our network, so this is becoming
a bit of a pain for our poor network guys. The other odd thing is that the
firewall is only reporting one-way traffic, from the server to the client,
but the client is not sending any traffic back down unless it is actively
connected to the remote server.
Any thoughts as to why this might be happening, or better yet, a way to cull
this traffic?
We're running MSSQL 2000 SP3a on Windows 2003 servers.
Thanks in advance!
Mike,
Have you applied the post-SP3a hotfix?
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
..
"Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
We're having a bit of an issue with network traffic being generated from one
of our MSSQL Servers.
It seems that when we launch Enterprise Manager on a remote computer
(usually at another office), the MSSQL servers start sending packets to the
EM regardless of whether we are maintaining an active connection to the
server or not. What is happening is that these packets are being lost and
reported in our firewall as 'host unreachable'. These packets are also
firing every second for each EM open across our network, so this is becoming
a bit of a pain for our poor network guys. The other odd thing is that the
firewall is only reporting one-way traffic, from the server to the client,
but the client is not sending any traffic back down unless it is actively
connected to the remote server.
Any thoughts as to why this might be happening, or better yet, a way to cull
this traffic?
We're running MSSQL 2000 SP3a on Windows 2003 servers.
Thanks in advance!
Mike,
|||We have the entire SP3a hotfix installed, but I am unaware of a post SP3a fix
- are you referring to SP4?
"Tom Moreau" wrote:

> Have you applied the post-SP3a hotfix?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
> news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
> We're having a bit of an issue with network traffic being generated from one
> of our MSSQL Servers.
> It seems that when we launch Enterprise Manager on a remote computer
> (usually at another office), the MSSQL servers start sending packets to the
> EM regardless of whether we are maintaining an active connection to the
> server or not. What is happening is that these packets are being lost and
> reported in our firewall as 'host unreachable'. These packets are also
> firing every second for each EM open across our network, so this is becoming
> a bit of a pain for our poor network guys. The other odd thing is that the
> firewall is only reporting one-way traffic, from the server to the client,
> but the client is not sending any traffic back down unless it is actively
> connected to the remote server.
> Any thoughts as to why this might be happening, or better yet, a way to cull
> this traffic?
> We're running MSSQL 2000 SP3a on Windows 2003 servers.
> Thanks in advance!
> Mike,
>
|||Define "entire SP3a hotfix". There is the service pack - SP3a - and then
there is the hotfix. Are you saying that you have applied SP3a but not the
hotfix? IOW, have you applied:
http://support.microsoft.com/kb/821277
Tom
Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
SQL Server MVP
Toronto, ON Canada
..
"Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
news:5D90B16F-7EDB-401C-8022-106365D44347@.microsoft.com...
We have the entire SP3a hotfix installed, but I am unaware of a post SP3a
fix
- are you referring to SP4?
"Tom Moreau" wrote:

> Have you applied the post-SP3a hotfix?
> --
> Tom
> ----
> Thomas A. Moreau, BSc, PhD, MCSE, MCDBA
> SQL Server MVP
> Toronto, ON Canada
> ..
> "Mike Schurkin" <MikeSchurkin@.discussions.microsoft.com> wrote in message
> news:C948BB2C-1A9D-4B73-9BDF-72B74A1FA9A2@.microsoft.com...
> We're having a bit of an issue with network traffic being generated from
> one
> of our MSSQL Servers.
> It seems that when we launch Enterprise Manager on a remote computer
> (usually at another office), the MSSQL servers start sending packets to
> the
> EM regardless of whether we are maintaining an active connection to the
> server or not. What is happening is that these packets are being lost and
> reported in our firewall as 'host unreachable'. These packets are also
> firing every second for each EM open across our network, so this is
> becoming
> a bit of a pain for our poor network guys. The other odd thing is that
> the
> firewall is only reporting one-way traffic, from the server to the client,
> but the client is not sending any traffic back down unless it is actively
> connected to the remote server.
> Any thoughts as to why this might be happening, or better yet, a way to
> cull
> this traffic?
> We're running MSSQL 2000 SP3a on Windows 2003 servers.
> Thanks in advance!
> Mike,
>

Hiding SQL server

I'm trying to hide a SQL server, to prevent anyone from knowing it exists. I
checked the option 'Hide server' in the server network utility, however, whe
n
adding a new SQL server registration in Enterprise manager on another machin
e
then clicking the browse button, my hidden server is happily displayed.
Any ideas on how to effectively hide the server?Disable access to UDP port 1434. What are you really trying to hide though,
people can still scan and find tcp 1433 unless you change that too...
"HALi" <HALi@.discussions.microsoft.com> wrote in message
news:FB25C73B-1794-4743-872A-A2C8FD9016F4@.microsoft.com...
> I'm trying to hide a SQL server, to prevent anyone from knowing it exists.
> I
> checked the option 'Hide server' in the server network utility, however,
> when
> adding a new SQL server registration in Enterprise manager on another
> machine
> then clicking the browse button, my hidden server is happily displayed.
> Any ideas on how to effectively hide the server?|||Firewall it.
I administered an HR server and that was firewalled. Only 1433 was
opened and only certain IP addresses on the network was allowed to
connect to the machine - my workstation being one of them.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
HALi wrote:
> I'm trying to hide a SQL server, to prevent anyone from knowing it exists.
I
> checked the option 'Hide server' in the server network utility, however, w
hen
> adding a new SQL server registration in Enterprise manager on another mach
ine
> then clicking the browse button, my hidden server is happily displayed.
> Any ideas on how to effectively hide the server?

Hiding instances on the n/w (Port 1434)

Hi,
I tried to hide an instance of MSSQL2000 SP3 on the n/w by first removing
all the enabled protocols using the server network utility which worked fine,
i then renabled the TCP/IP protocol and selected hide server which seemed to
switch the port number to 2433, which i understand has an implication for
clients regarding connection strings including port numbers, aliasing etc.
I then switched the port number back to 1433 and de-selected the hide server
option but now i can connect to the machine using query analyzer when i know
the machine name but if i try to hit the button which lists all servers on
the n/w the server does not appear. I believe this list is populated based on
a n/w port scan which builds the list based on machines that respond to a
request on UDP port 1434.
If anyone knows why the server will not appear i would appreciate a pointer,
i have also attempted to find help about blocking on port 1434 but cannot
find help on how to do so, keep getting instructions on blocking at the
firewall, i just want to understand how this works.
Thanks in advance
Pat
Pmcg,
You cannot prevent SQL Server listening on port 1434. If you want to prevent
clients accessing this port, you have no choice but to use a firewall.
SQL Server's enumeration mechanism can only list servers that are registered
in Enterprise Manager, and ones that are on your subnet - the broadcast does
not work across routers or firewalls. Perhaps this is the problem.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Pmcg" wrote:

> Hi,
> I tried to hide an instance of MSSQL2000 SP3 on the n/w by first removing
> all the enabled protocols using the server network utility which worked fine,
> i then renabled the TCP/IP protocol and selected hide server which seemed to
> switch the port number to 2433, which i understand has an implication for
> clients regarding connection strings including port numbers, aliasing etc.
> I then switched the port number back to 1433 and de-selected the hide server
> option but now i can connect to the machine using query analyzer when i know
> the machine name but if i try to hit the button which lists all servers on
> the n/w the server does not appear. I believe this list is populated based on
> a n/w port scan which builds the list based on machines that respond to a
> request on UDP port 1434.
> If anyone knows why the server will not appear i would appreciate a pointer,
> i have also attempted to find help about blocking on port 1434 but cannot
> find help on how to do so, keep getting instructions on blocking at the
> firewall, i just want to understand how this works.
>
> Thanks in advance
> Pat

Hiding instances on the n/w (Port 1434)

Hi,
I tried to hide an instance of MSSQL2000 SP3 on the n/w by first removing
all the enabled protocols using the server network utility which worked fine
,
i then renabled the TCP/IP protocol and selected hide server which seemed to
switch the port number to 2433, which i understand has an implication for
clients regarding connection strings including port numbers, aliasing etc.
I then switched the port number back to 1433 and de-selected the hide server
option but now i can connect to the machine using query analyzer when i know
the machine name but if i try to hit the button which lists all servers on
the n/w the server does not appear. I believe this list is populated based o
n
a n/w port scan which builds the list based on machines that respond to a
request on UDP port 1434.
If anyone knows why the server will not appear i would appreciate a pointer,
i have also attempted to find help about blocking on port 1434 but cannot
find help on how to do so, keep getting instructions on blocking at the
firewall, i just want to understand how this works.
Thanks in advance
PatPmcg,
You cannot prevent SQL Server listening on port 1434. If you want to prevent
clients accessing this port, you have no choice but to use a firewall.
SQL Server's enumeration mechanism can only list servers that are registered
in Enterprise Manager, and ones that are on your subnet - the broadcast does
not work across routers or firewalls. Perhaps this is the problem.
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Pmcg" wrote:

> Hi,
> I tried to hide an instance of MSSQL2000 SP3 on the n/w by first removing
> all the enabled protocols using the server network utility which worked fi
ne,
> i then renabled the TCP/IP protocol and selected hide server which seemed
to
> switch the port number to 2433, which i understand has an implication for
> clients regarding connection strings including port numbers, aliasing etc.
> I then switched the port number back to 1433 and de-selected the hide serv
er
> option but now i can connect to the machine using query analyzer when i kn
ow
> the machine name but if i try to hit the button which lists all servers on
> the n/w the server does not appear. I believe this list is populated based
on
> a n/w port scan which builds the list based on machines that respond to a
> request on UDP port 1434.
> If anyone knows why the server will not appear i would appreciate a pointe
r,
> i have also attempted to find help about blocking on port 1434 but cannot
> find help on how to do so, keep getting instructions on blocking at the
> firewall, i just want to understand how this works.
>
> Thanks in advance
> Pat

Hiding instances on the n/w (Port 1434)

Hi,
I tried to hide an instance of MSSQL2000 SP3 on the n/w by first removing
all the enabled protocols using the server network utility which worked fine,
i then renabled the TCP/IP protocol and selected hide server which seemed to
switch the port number to 2433, which i understand has an implication for
clients regarding connection strings including port numbers, aliasing etc.
I then switched the port number back to 1433 and de-selected the hide server
option but now i can connect to the machine using query analyzer when i know
the machine name but if i try to hit the button which lists all servers on
the n/w the server does not appear. I believe this list is populated based on
a n/w port scan which builds the list based on machines that respond to a
request on UDP port 1434.
If anyone knows why the server will not appear i would appreciate a pointer,
i have also attempted to find help about blocking on port 1434 but cannot
find help on how to do so, keep getting instructions on blocking at the
firewall, i just want to understand how this works.
Thanks in advance
PatPmcg,
You cannot prevent SQL Server listening on port 1434. If you want to prevent
clients accessing this port, you have no choice but to use a firewall.
SQL Server's enumeration mechanism can only list servers that are registered
in Enterprise Manager, and ones that are on your subnet - the broadcast does
not work across routers or firewalls. Perhaps this is the problem.
--
Mark Allison, SQL Server MVP
http://www.markallison.co.uk
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602m.html
"Pmcg" wrote:
> Hi,
> I tried to hide an instance of MSSQL2000 SP3 on the n/w by first removing
> all the enabled protocols using the server network utility which worked fine,
> i then renabled the TCP/IP protocol and selected hide server which seemed to
> switch the port number to 2433, which i understand has an implication for
> clients regarding connection strings including port numbers, aliasing etc.
> I then switched the port number back to 1433 and de-selected the hide server
> option but now i can connect to the machine using query analyzer when i know
> the machine name but if i try to hit the button which lists all servers on
> the n/w the server does not appear. I believe this list is populated based on
> a n/w port scan which builds the list based on machines that respond to a
> request on UDP port 1434.
> If anyone knows why the server will not appear i would appreciate a pointer,
> i have also attempted to find help about blocking on port 1434 but cannot
> find help on how to do so, keep getting instructions on blocking at the
> firewall, i just want to understand how this works.
>
> Thanks in advance
> Pat