Connecting to local instance with firewall client enabled

I'm running SQL Server 2000 SP3 on my XP Pro laptop and everything
works fine without firewall client enabled. When I VPN in to the
network and enable the ISA server firewall client, I can't connect to
my local instance using Enterprise Manager or Query Analyzer, although
I can connect to another instance running on a server on the network.
If I'm VPNed in and I don't enable firewall client, I can still
connect to the local instance. And interestingly my ASP.NET
application (running locally) can still connect to the local SQL
Server instance once I changed the server name in web.config from
localhost to chris-laptop.
Any help would be greatly appreciated, as I really need to have
firewall client enabled and access to my databases through query
analyser at the same time.
Thanks
Chris BettertonIf you specifiy the ip address that SQL Server is listening on when
attempting to connect via Query Analyzer, does it allow you to connect?
If it does then you can use the SQL CLient Network Utility to create an
alias that points the server name to the ip address. This would let you
connect using the server name.
Rand
This posting is provided "as is" with no warranties and confers no rights.|||Hadn't thought of that, 127.0.0.1 works fine so I can use the alias
approach. Thanks for your help.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Connecting to local instance with firewall client enabled

I'm running SQL Server 2000 SP3 on my XP Pro laptop and everything
works fine without firewall client enabled. When I VPN in to the
network and enable the ISA server firewall client, I can't connect to
my local instance using Enterprise Manager or Query Analyzer, although
I can connect to another instance running on a server on the network.
If I'm VPNed in and I don't enable firewall client, I can still
connect to the local instance. And interestingly my ASP.NET
application (running locally) can still connect to the local SQL
Server instance once I changed the server name in web.config from
localhost to chris-laptop.
Any help would be greatly appreciated, as I really need to have
firewall client enabled and access to my databases through query
analyser at the same time.
Thanks
Chris Betterton
If you specifiy the ip address that SQL Server is listening on when
attempting to connect via Query Analyzer, does it allow you to connect?
If it does then you can use the SQL CLient Network Utility to create an
alias that points the server name to the ip address. This would let you
connect using the server name.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||Hadn't thought of that, 127.0.0.1 works fine so I can use the alias
approach. Thanks for your help.
*** Sent via Developersdex http://www.codecomments.com ***
Don't just participate in USENET...get rewarded for it!

Connecting Sql Server Yukon

Folks, i've just installed the express edition and have enabled all the protocols within the COMPUTER MANAGER. When i try connecting the INSTANCE through QA or EM, sql doesn't exist or access denied.
I've installed the default instance.
Please guide.a friend of mine had a similar problem,
check
http://www.sqlteam.com/forums/topic.asp?TOPIC_ID=38264|||Hi, sorry for lack of knowledge. Can't i even connect to the db engine through QA. How do i interact with the database?
There is only SQL COMPUTER MANAGER in the Installation Menu.
There isn't any client tool under
C:\Program Files\Microsoft SQL Server\90\Tools\binn.

Please guide.|||There are no client tools for SQL Express. QA and EM don't work with it. You can use the command line utility included with it. You can also connect using .NET if you have web matrix or VS.NET.|||Thank you guys.

CONNECTING SQL 2005 SERVER FROM A REMOTE MACHINE PROBLEM

I installed SQL 2005 with some settings which is below.
INSTANCE NAME: CAVCAV
Protocols For CAVCAV :
Shared Memory : Enabled
Named Pipes : Enabled , Pipe Name :\\.\pipe\MSSQL$CAVCAVsql\query
TCP/IP : Enabled Yes
Ip address :
Ip1
active:yes
enabled :yes
Ip Adress : 212.154.38.146
Tcp Dynamic Ports :
Tcp Port : 1433
Ip2
active:yes
enabled :yes
Ip Adress :127.0.0.1
Tcp Dynamic Ports :
Tcp Port : 1433
IpAll
Tcp Dynamic Ports :
Tcp Port : 1433
VIA : Disabled
Sql Native Client Configuration
Client Protocols
Shared Memory : Enabled
Named Pipes : Enabled , Default Pipe :sql\query
VIA : Disabled
Telnet 212.154.38.146 1433 (Success)
I can connect to server from my local MSSMS (SQL 2005.)
When I try to connect vie DSN or Access (Linked Table Manager) Or SQL 2000
Enterprise Manager I cant connect.
When I write Only Ip address which is 212.154.38.146 on System DSN
I get
Attempting connection
[Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid connection.
TESTS FAILED!
When I write 212.154.38.146\CAVCAV
I get
Microsoft SQL Server ODBC Driver Version 03.86.3959
Running connectivity tests...
Attempting connection
[Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
access denied.
TESTS FAILED!
How can i connect and manage my Sql 2005 remotely. Any help will be
appreciated.Did you enable remote connections?
MC
<in da club> wrote in message news:epyXh4PAIHA.484@.TK2MSFTNGP06.phx.gbl...
>I installed SQL 2005 with some settings which is below.
> INSTANCE NAME: CAVCAV
> Protocols For CAVCAV :
> Shared Memory : Enabled
> Named Pipes : Enabled , Pipe Name :\\.\pipe\MSSQL$CAVCAVsql\query
> TCP/IP : Enabled Yes
> Ip address :
> Ip1
> active:yes
> enabled :yes
> Ip Adress : 212.154.38.146
> Tcp Dynamic Ports :
> Tcp Port : 1433
> Ip2
> active:yes
> enabled :yes
> Ip Adress :127.0.0.1
> Tcp Dynamic Ports :
> Tcp Port : 1433
> IpAll
> Tcp Dynamic Ports :
> Tcp Port : 1433
>
> VIA : Disabled
> Sql Native Client Configuration
> Client Protocols
> Shared Memory : Enabled
> Named Pipes : Enabled , Default Pipe :sql\query
> VIA : Disabled
>
> Telnet 212.154.38.146 1433 (Success)
> I can connect to server from my local MSSMS (SQL 2005.)
> When I try to connect vie DSN or Access (Linked Table Manager) Or SQL 2000
> Enterprise Manager I cant connect.
> When I write Only Ip address which is 212.154.38.146 on System DSN
> I get
> Attempting connection
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid connection.
> TESTS FAILED!
> When I write 212.154.38.146\CAVCAV
> I get
> Microsoft SQL Server ODBC Driver Version 03.86.3959
> Running connectivity tests...
> Attempting connection
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> TESTS FAILED!
> How can i connect and manage my Sql 2005 remotely. Any help will be
> appreciated.
>
>
>
>
>
>
>
>|||Go to SQL Server Surface Area Configuration and check your instance if
Remote Connections is enabled as TCP\IP as MC mentioned.
Remote Connections feature is disabled by default for Developer and Express
Editions.
And check out if Browser Service is running and use
<computer_name>\<instance_name> in your connection strings.
--
Ekrem Önsoy
<in da club> wrote in message news:epyXh4PAIHA.484@.TK2MSFTNGP06.phx.gbl...
>I installed SQL 2005 with some settings which is below.
> INSTANCE NAME: CAVCAV
> Protocols For CAVCAV :
> Shared Memory : Enabled
> Named Pipes : Enabled , Pipe Name :\\.\pipe\MSSQL$CAVCAVsql\query
> TCP/IP : Enabled Yes
> Ip address :
> Ip1
> active:yes
> enabled :yes
> Ip Adress : 212.154.38.146
> Tcp Dynamic Ports :
> Tcp Port : 1433
> Ip2
> active:yes
> enabled :yes
> Ip Adress :127.0.0.1
> Tcp Dynamic Ports :
> Tcp Port : 1433
> IpAll
> Tcp Dynamic Ports :
> Tcp Port : 1433
>
> VIA : Disabled
> Sql Native Client Configuration
> Client Protocols
> Shared Memory : Enabled
> Named Pipes : Enabled , Default Pipe :sql\query
> VIA : Disabled
>
> Telnet 212.154.38.146 1433 (Success)
> I can connect to server from my local MSSMS (SQL 2005.)
> When I try to connect vie DSN or Access (Linked Table Manager) Or SQL 2000
> Enterprise Manager I cant connect.
> When I write Only Ip address which is 212.154.38.146 on System DSN
> I get
> Attempting connection
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]Invalid connection.
> TESTS FAILED!
> When I write 212.154.38.146\CAVCAV
> I get
> Microsoft SQL Server ODBC Driver Version 03.86.3959
> Running connectivity tests...
> Attempting connection
> [Microsoft][ODBC SQL Server Driver][DBNETLIB]SQL Server does not exist or
> access denied.
> TESTS FAILED!
> How can i connect and manage my Sql 2005 remotely. Any help will be
> appreciated.
>
>
>
>
>
>
>
>|||Remote Connections is enabled
Local and Remote Connections
* using both tcp/ip and named pipes
Im able to connect it from my local SQL 2005 Management Studio too.
Sql Server Browser Service is running too. I use Enterprise edition.|||Did you check your firewall settings? Be sure 1433 is allowed.
--
Ekrem Önsoy
<in da club> wrote in message news:ODZjlkQAIHA.4584@.TK2MSFTNGP03.phx.gbl...
> Remote Connections is enabled
> Local and Remote Connections
> * using both tcp/ip and named pipes
> Im able to connect it from my local SQL 2005 Management Studio too.
> Sql Server Browser Service is running too. I use Enterprise edition.
>|||I can
Telnet 212.154.38.146 1433 with Success . Im sure it is open .
One more thing when i netstat -an
there are some records like that
127.0.0.1:1000 127.0.0.0:1433 TIME_WAIT
127.0.0.1:1001 127.0.0.0:1433 TIME_WAIT
.
.
127.0.0.1:3000 127.0.0.0:1433 TIME_WAIT
Im sure dynamic tcp port is blank and TCP port is 1433
Im very confused. Almost everthing seems ok but im not able to connect it
via DSN and SQL 2000 Server.|||I solved the problem.
If you use only named instance you need 1434 udp port open + 1435 tcp
2) SQL Browser service: which is a replacement of SSRP system in SQL Server
2000, run as a Windows Service on installation of SQL 2k5. Upon startup, SQL
Server Browser starts and claims UDP port 1434. When SQL Server 2000 and SQL
Server 2005 clients request SQL Server resources, the client network library
sends a UDP message to the server using port 1434. SQL Server Browser
responds with the TCP/IP port or named pipe of the requested instance.
Therefore, you need to make sure SQL Browser is enabled and started when
remote client ask for which tcp port or pipe name SQL Server is listening
on. If your remote SQL Instance is a default instance, you do not necessary
enable sql browser since client would always try default TCP port 1433 and
pipe name \\<remoterserver>\pipe\sql\query. But, if you have SQL 2k5 named
instance installed or SQL 2000 and SQL 2k5 side by side installed, you must
enable and start sqlbrowser.
II. Problem list:
By understanding background 1) and 2), I belive you can imagine issues you
may face when make remote connection against SQL 2k5:
1) Fail to connect over TCP/IP or Named Pipe if the request protocol was
not enabled.
2) Fail to connect over TCP/IP or Named Pipe if Firewall enabled on the
remote server and tcp port or "File and Printer Sharing" is not added to
the Firewall exception list.
3) Fail to connect to remote sql named instance if SQL Browser was not
enabled or UDP port 1434 that browser listening on is added to the Firewall
exception list.

Connecting remotely without any issues.

I already have local and remote connections enabled. What else do I have to
enable? Also, I have installed all components I thought possible. How do I
access or install Data Transforation Project in 2005?
"Geoff N. Hiten" wrote:

> Login locally to the server and run the SQL Surface Area Configuration Too
l.
> SQL 2005 is "secure by default". One aspect of this is the SQL server
> disables all external network connections by default. You can connect
> locally on the box, but not across the network. This allows a DBA to load
> and patch a SQL server without exposing it to network attacks like a SQL
> 2000 system.
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVPericzaj wrote:
> I already have local and remote connections enabled. What else do I have t
o
> enable? Also, I have installed all components I thought possible. How do I
> access or install Data Transforation Project in 2005?
>
Do you mean DTS (Data Transformation Services)? That no longer exists
in SQL 2005, it has been replaced with SSIS (SQL Server Integration
Services).
Tracy McKibben
MCDBA
http://www.realsqlguy.com

Connecting remotely without any issues.

I already have local and remote connections enabled. What else do I have to
enable? Also, I have installed all components I thought possible. How do I
access or install Data Transforation Project in 2005?
"Geoff N. Hiten" wrote:
> Login locally to the server and run the SQL Surface Area Configuration Tool.
> SQL 2005 is "secure by default". One aspect of this is the SQL server
> disables all external network connections by default. You can connect
> locally on the box, but not across the network. This allows a DBA to load
> and patch a SQL server without exposing it to network attacks like a SQL
> 2000 system.
>
> --
> Geoff N. Hiten
> Senior Database Administrator
> Microsoft SQL Server MVPericzaj wrote:
> I already have local and remote connections enabled. What else do I have to
> enable? Also, I have installed all components I thought possible. How do I
> access or install Data Transforation Project in 2005?
>
Do you mean DTS (Data Transformation Services)? That no longer exists
in SQL 2005, it has been replaced with SSIS (SQL Server Integration
Services).
Tracy McKibben
MCDBA
http://www.realsqlguy.com