Cannot connect to SQL Express on 2003 Machine from XP machine

Hi,
Can someone help me with a connection problem!
I am trying to connect from an XP SP2 machine remotely to a SQL Express
database on a 2003 server.
Everytime I try to connect via Visual Web Developer, i get the
following error:
"An error has occurred while establishing connection to the server.
When connecting to SQL Server 2005, this failure may be caused by the
fact that under the default settings SQL Server does not allow remote
connections. (provider: Named Pipes Provider, error: 40 - Could not
open a connection to SQL Server)"
I have tried:
- In Surface Area Configuration for Services. . . Enabled "Local and
Remote connections", Checked "Using Both TCP/IP and Names Pipes"
- In SQL Server configuration manager, under 'Protocols for SQL
Express', gone to properties of TCP/IP and then IP Addresses. Here i
have put a 0 for TCP Dynamic Ports and 1433 for TCP Port.
- Enabled Remote Admin Connections, 1 in SQLExpress.
The connection string I am trying to use is: xx.xxx.xx.xx/SQLEXPRESS
All this and still no joy!
Can anyone help or provide more ideas on what I could try!!!
Thanks
H
Have you checked the Windows XP Firewall to see if port 1433 (MSSQL) is
blocked?
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
<harrys@.gmail.com> wrote in message
news:1162418209.991142.71240@.i42g2000cwa.googlegro ups.com...
> Hi,
> Can someone help me with a connection problem!
> I am trying to connect from an XP SP2 machine remotely to a SQL Express
> database on a 2003 server.
> Everytime I try to connect via Visual Web Developer, i get the
> following error:
> "An error has occurred while establishing connection to the server.
> When connecting to SQL Server 2005, this failure may be caused by the
> fact that under the default settings SQL Server does not allow remote
> connections. (provider: Named Pipes Provider, error: 40 - Could not
> open a connection to SQL Server)"
>
> I have tried:
> - In Surface Area Configuration for Services. . . Enabled "Local and
> Remote connections", Checked "Using Both TCP/IP and Names Pipes"
> - In SQL Server configuration manager, under 'Protocols for SQL
> Express', gone to properties of TCP/IP and then IP Addresses. Here i
> have put a 0 for TCP Dynamic Ports and 1433 for TCP Port.
> - Enabled Remote Admin Connections, 1 in SQLExpress.
> The connection string I am trying to use is: xx.xxx.xx.xx/SQLEXPRESS
> All this and still no joy!
> Can anyone help or provide more ideas on what I could try!!!
> Thanks
> H
>
|||Yep - Running Zone Alarm, so even switched it off completely to test.
But I have another 2000 server that I can connect to fine, so it's
definitely a problem on the 2003 server.
No matter what I do, it doesn't seem to want to open the port!
Any ideas anyone else?
Thanks
H
Arnie Rowland wrote:[vbcol=seagreen]
> Have you checked the Windows XP Firewall to see if port 1433 (MSSQL) is
> blocked?
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to the
> top yourself.
> - H. Norman Schwarzkopf
>
> <harrys@.gmail.com> wrote in message
> news:1162418209.991142.71240@.i42g2000cwa.googlegro ups.com...
|||And is port 1434 (for the SQLBrowser service) also open.
Arnie Rowland, Ph.D.
Westwood Consulting, Inc
Most good judgment comes from experience.
Most experience comes from bad judgment.
- Anonymous
You can't help someone get up a hill without getting a little closer to the
top yourself.
- H. Norman Schwarzkopf
<harrys@.gmail.com> wrote in message
news:1162467876.092108.66640@.m7g2000cwm.googlegrou ps.com...
> Yep - Running Zone Alarm, so even switched it off completely to test.
> But I have another 2000 server that I can connect to fine, so it's
> definitely a problem on the 2003 server.
> No matter what I do, it doesn't seem to want to open the port!
> Any ideas anyone else?
> Thanks
> H
>
> Arnie Rowland wrote:
>
|||Yep it is. Even to be sure have opened UDP and TCP.
Probaly should have checked this before, but having just done a
'netstat -a' command, it seems that the 2003 server is not listening on
port 1433.
Any idea on what I can do to get it 'listening'?!
Thanks
H
Arnie Rowland wrote:[vbcol=seagreen]
> And is port 1434 (for the SQLBrowser service) also open.
> --
> Arnie Rowland, Ph.D.
> Westwood Consulting, Inc
> Most good judgment comes from experience.
> Most experience comes from bad judgment.
> - Anonymous
> You can't help someone get up a hill without getting a little closer to the
> top yourself.
> - H. Norman Schwarzkopf
>
> <harrys@.gmail.com> wrote in message
> news:1162467876.092108.66640@.m7g2000cwm.googlegrou ps.com...
|||Check the logs for the EXPRESS instance to see what port it
is listening on, what protocols, any issues with the
protocols and listening ports. It will log all that
information at start up.
You said you are using xx.xxx.xx.xx/SQLEXPRESS
for the connection string. That should be
xx.xxx.xx.xx\SQLEXPRESS
Make sure the browser service is actually running.
You will also want to make sure you can connect locally
before trying remotely.
-Sue
On 3 Nov 2006 03:00:49 -0800, harrys@.gmail.com wrote:
[vbcol=seagreen]
>Yep it is. Even to be sure have opened UDP and TCP.
>Probaly should have checked this before, but having just done a
>'netstat -a' command, it seems that the 2003 server is not listening on
>port 1433.
>Any idea on what I can do to get it 'listening'?!
>Thanks
>H
>
>Arnie Rowland wrote:
|||Thanks for the checks Sue.
Looking at the log's it says:
Server is listening on [ 'any' <ipv4> 1433].
And this is on the Express instance.
But yet, it doesn't show up when doing the netstat -a command?
And i double checked the connection string, and i did have it the right
way round. Just a typo on here on my part!
Any other suggestions anyone?
Thanks
H
Sue Hoegemeier wrote:[vbcol=seagreen]
> Check the logs for the EXPRESS instance to see what port it
> is listening on, what protocols, any issues with the
> protocols and listening ports. It will log all that
> information at start up.
> You said you are using xx.xxx.xx.xx/SQLEXPRESS
> for the connection string. That should be
> xx.xxx.xx.xx\SQLEXPRESS
> Make sure the browser service is actually running.
> You will also want to make sure you can connect locally
> before trying remotely.
> -Sue
> On 3 Nov 2006 03:00:49 -0800, harrys@.gmail.com wrote:
|||Actually, just going through the event viewer, i did find this entry:
The configuration of the AdminConnection\TCP protocol in the SQL
instance SQLEXPRESS is not valid.
Any one know what this means or how i fix it? Sounds like it could be
the source of my problems?
Thanks
H
Harry wrote:[vbcol=seagreen]
> Thanks for the checks Sue.
> Looking at the log's it says:
> Server is listening on [ 'any' <ipv4> 1433].
> And this is on the Express instance.
> But yet, it doesn't show up when doing the netstat -a command?
>
> And i double checked the connection string, and i did have it the right
> way round. Just a typo on here on my part!
> Any other suggestions anyone?
> Thanks
> H
>
> Sue Hoegemeier wrote:
|||Is the event source SQLBrowser ?
That would be my guess. I'd look for SQLBrowser service
listening on UDP 1434 using netstat -abn, check for any
conflicts on 1434.
Make sure the Browser service is actually running, not just
started.
Do you have a default instance on this box? Are there any
conflicts on TCP 1434? Did you check the properties and
configurations for the TCP/IP protocol on the instance(s)?
Those are the areas you'd probably want to check.
-Sue
On 3 Nov 2006 10:21:23 -0800, "Harry" <harrys@.gmail.com>
wrote:
[vbcol=seagreen]
>Actually, just going through the event viewer, i did find this entry:
>The configuration of the AdminConnection\TCP protocol in the SQL
>instance SQLEXPRESS is not valid.
>Any one know what this means or how i fix it? Sounds like it could be
>the source of my problems?
>Thanks
>H
>
>Harry wrote: