Re: SQL Connection in Workgroup

Tech-Archive recommends: Fix windows errors by optimizing your registry

I have configured the surface configuration to use TCP/IP and Named ports but
this has not worked (this caught me out with a previour install).

The browser service is running
I will try and open UDP port 1434

Where can I get the SQL Server Client connectivity?

"Rick Byham, (MSFT)" wrote:


When connecting to SQL Server 2005 or 2008, your laptop asks the XP machine
what port is the named instance ComputerName\SQLEXPRESS listening on. The
SQL Server Browser Service on the XP computer uses UDP port 1434 to send
back the answer, such as TCP port 1234. So try opening UDP port 1434 on the
XP computer. And make sure the SQL Server Browser Service is started.

Also, the SQL Server error log will tell you what port SQL Server is
listening on. Look it up. Let's say it's TCP port 1434. You can try to
connect to ComputerName,portnumber like ComputerName,1434
That should bypass the name to port resolution issue. Not convenient but
useful for testing.

Also, your client is using DBNETLIB instead of the SQL Server Native Client.
This is allowed, but you might want to install the SQL Server 2005 client
connectivity on the laptop.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.

"Jo" <Jo@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3B3A2E8F-8AED-4028-9382-D52C07F533EB@xxxxxxxxxxxxxxxx
Hi I have a small problem.

I have SQL Server Express installed on an XP workstation in workgroup. My
database app is working well on the machine.

However I am unable to connect to the database from my laptop. I get the
error:

[DBNETLIB]{connectionopen (connect()).] SQLServer does not exist or access
dennied

System Details:

SQL Server Mahine:
O\S - Windows XP SP2
Workgroup: MYHOME
Firewall: Windows firewall
Exception set up for SQL Program and TCP/IP Ports 1433, 1434,
1443
SQLVersion: SQL Express 2005

Laptop:
O\S - Windows XP SP2
Workgroup: MYHOME
Firewall Switched off

I have the same user account and password on both machines.

I am able to browse to shared directories on the SQL Machine.

Any help would be appreciated as I am struggleing.

Thanks,
Jolyon

.

Relevant Pages

  • Re: Bind failed on TCP port 1433
    ... It does sound like something is checking or blocking the port. ... Can we assume that once started SQL Server works OK? ... > fresh operating system install and is running SQL Server along with a ...
    (microsoft.public.sqlserver.setup)
  • Re: ADP problems after SQL 2005 Upgrade
    ... Use the SQL Server Configuration Manager to create aliases; ... each port can be associated only with a single instance. ... Sylvain Lafontaine, ing. ...
    (microsoft.public.access.adp.sqlserver)
  • Re: How to connect a workstation to SQL Server 2005 thru ODBC?
    ... that the client computer will have SQL Server 2005 component installed. ... > Welcome to the Getting Started with the Database Engine tutorial. ... see Running Setup to Install AdventureWorks Sample Databases ... Configuring a Fixed Port ...
    (microsoft.public.sqlserver.connect)
  • [NT] Microsoft SQL Server 2000 Unauthenticated System Compromise
    ... The following security advisory is sent to the securiteam mailing list, and can be found at the SecuriTeam web site: http://www.securiteam.com ... Microsoft's database server SQL Server 2000 exhibits two buffer-overrun ... clients connecting to TCP port 1433 or both. ... This message is a single byte packet, ...
    (Securiteam)
  • Re: Do SqlServer 2000 & SqlServer 2005 co-exist
    ... Either SQL Server 2000 or SQL Server 2005. ... So you have to move one of them to another port. ... You could allow an program exception in your firewall instead of a port number exception. ... I understand that you can connect to SQL 2000 named instance on the local ...
    (microsoft.public.sqlserver.setup)