Strange connection problem

[Greg Hines]

Hi Everyone,

MSDE2000 installed on 2003 Server.

With Windows Firewall turned ON, users in the same workgroup as the 2003
Server can connect to the SQL Database. Users on a different Workgroups
cannot connect to the SQL Database using either IP or ComputerName.

With the Firewall turned OFF, all users from all Workgroups can connect to
the SQL Database.

Can anyone explain to me why users in the same Workgroup can connect to the
SQL Database with the Firewall ON, while the Firewall must be turned OFF to
enable users from a different Workgroup to connect?

TIA

Greg

[Erland Sommarskog]

Greg Hines (gh****@aussiemail.com.au_NO_SPAM) writes:

MSDE2000 installed on 2003 Server.

With Windows Firewall turned ON, users in the same workgroup as the 2003
Server can connect to the SQL Database. Users on a different Workgroups
cannot connect to the SQL Database using either IP or ComputerName.

With the Firewall turned OFF, all users from all Workgroups can connect to
the SQL Database.

Can anyone explain to me why users in the same Workgroup can connect to
the SQL Database with the Firewall ON, while the Firewall must be turned
OFF to enable users from a different Workgroup to connect?

I assume the users connect with SQL authentication?

I would look for the answer in the firewall configuration. The default
is that no one could connect to SQL Server when Windows Firewall is on.
So if users in the same workgroup can connect, I suspect that someone
open port 1433 in the firewall. But possibly he only opened the port for
some IP addresses?
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

[Greg Hines]

"Erland Sommarskog" <es****@sommarskog.sewrote in message
news:Xn**********************@127.0.0.1...

Greg Hines (gh****@aussiemail.com.au_NO_SPAM) writes:

>MSDE2000 installed on 2003 Server.

With Windows Firewall turned ON, users in the same workgroup as the 2003
Server can connect to the SQL Database. Users on a different Workgroups
cannot connect to the SQL Database using either IP or ComputerName.

With the Firewall turned OFF, all users from all Workgroups can connect
to
the SQL Database.

Can anyone explain to me why users in the same Workgroup can connect to
the SQL Database with the Firewall ON, while the Firewall must be turned
OFF to enable users from a different Workgroup to connect?

I assume the users connect with SQL authentication?

I would look for the answer in the firewall configuration. The default
is that no one could connect to SQL Server when Windows Firewall is on.
So if users in the same workgroup can connect, I suspect that someone
open port 1433 in the firewall. But possibly he only opened the port for
some IP addresses?

Yes, SQL authentication only.

I've found nothing about any firewall ports being open. So I opened port
445 (Named Pipes) and I'm still getting the same results. Seems very
strange to me.

Greg

[Erland Sommarskog]

Greg Hines (gh****@aussiemail.com.au_NO_SPAM) writes:

I've found nothing about any firewall ports being open. So I opened port
445 (Named Pipes) and I'm still getting the same results. Seems very
strange to me.

In Control Panel, click Windows Firewall. Check the Expressions tab. You
may have SQL Server listed. In such case click Edit, and look under the
button Change scope.
--
Erland Sommarskog, SQL Server MVP, es****@sommarskog.se

Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/pro...ads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx

[Greg Hines]

In Control Panel, click Windows Firewall. Check the Expressions tab. You

may have SQL Server listed. In such case click Edit, and look under the
button Change scope.

Will do that's a great idea. Thanks.