Re: Strange connection problem
- From: Erland Sommarskog <esquel@xxxxxxxxxxxxx>
- Date: Tue, 27 May 2008 21:14:03 +0000 (UTC)
Greg Hines (ghines@xxxxxxxxxxxxxxxxxxxxxxxxx) 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, esquel@xxxxxxxxxxxxx
Books Online for SQL Server 2005 at
http://www.microsoft.com/technet/prodtechnol/sql/2005/downloads/books.mspx
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx
.
- Follow-Ups:
- Re: Strange connection problem
- From: Greg Hines
- Re: Strange connection problem
- References:
- Strange connection problem
- From: Greg Hines
- Strange connection problem
- Prev by Date: Re: confusion over indexs via primary key and clustered index
- Next by Date: Re: Help with an Update Statment
- Previous by thread: Strange connection problem
- Next by thread: Re: Strange connection problem
- Index(es):
Relevant Pages
|
