Re: Cannot connect to SQL Express on 2003 Machine from XP machine

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@xxxxxxxxx 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:
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@xxxxxxxxx> wrote in message
news:1162467876.092108.66640@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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:
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@xxxxxxxxx> wrote in message
news:1162418209.991142.71240@xxxxxxxxxxxxxxxxxxxxxxxxxxxxxxx
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



.

Relevant Pages

  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • Re: Still cant connect to RWW or OWA remotely
    ... it certainly appears to be something about the SBS configuration. ... Meridian.local Ethernet adapter Local Area Connection: ... Windows SMALL BUSINESS SERVER 2003 Windows IP Configuration ... 192.168.254.254) directly to a port on the router and then ...
    (microsoft.public.windows.server.sbs)
  • RE: VBscript Error on SBS2k3
    ... DHCP Server turned of SonicWALL with VPN Pass through request for IP to ... the problem should be caused by the 4125 port. ... > | Accessories and Communications and Remote Desktop Connection? ... > | 2.In Internet Explorer on the workstation you are connecting from, ...
    (microsoft.public.windows.server.sbs)
  • Re: interfaces lo:1 lo:2 lo:3? (for remote ssh tunnels)
    ... That's the problem tunneling (port forwarding) solves. ... >>can't get past the client firewall. ... > I don't understand why the server would be making the ... server initiates another connection to the client -- in this ...
    (Debian-User)
  • Re: Can not access Web and FTP sites from Internet
    ... your IP Configuration on the Server is correctly. ... Connecting To 12.208.215.87...Could not open connection to the host, ... 1> From the result, we can see the telnet failed, which means the router ... does not forward Port 443 to SBS Server. ...
    (microsoft.public.windows.server.sbs)