Re: SQLSMS - Cannot Connect SQL Server 2000
- From: JeffP-> <JeffP@xxxxxxxxxxxxxxxxxxxxxxxxx>
- Date: Thu, 15 Jan 2009 10:32:08 -0800
Whewww... it was a long & sorted path... After finding that I could connect
to a WinServer 2000, I set out to make sure that I could ping... hrs later
checking that port 445 is open, disconnected Win Firewall... still no go...
In my TrendMicro Security SMB console, I added to the TM Firewall -
SQLServer, Port 1433, TCP (not UDP) & only IP's in my LAN's range and viola,
I'm able to connect... aliases and etc were not the solution.
I fiddled w/so many security policies and other port issues, I really should
have known that it was either WinXP Firewall or TM's.
I'm a happy camper...
"Rick Byham, (MSFT)" wrote:
If I'm following this, the NewXP has SS 2005 tools. Try using SQL Server.
Configuration Manager (on the new XP computer), and on the left side select
SQL Native Client Configuration, Client Protocols.
On the right-side make sure TCP/IP is enabled. And make sure it's priority
is a lower "order" number than Named Pipes.
It's OK to have Shared Memory as order number 1.
But perhaps you have already checked this.
Anther idea: I take it the NewXP computer can ping the laptop by both IP
Address. Can it ping by name? Maybe the name resolution is stale. On the
NewXP computer, open a command prompt and execute ipconfig /flushdns
The next time you try to connect by name it will resolve the name to ip
address by contacting the name resolution service and get the most current
ip address. I have this trouble all the time when connecting to my laptop,
since my laptop is always changing it's ip address as I move around.
--
Rick Byham (MSFT), SQL Server Books Online
This posting is provided "AS IS" with no warranties, and confers no rights.
"JeffP->" <JeffP@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:7DA74A2D-D467-4A95-8ED8-F6BEBB18EDC9@xxxxxxxxxxxxxxxx
After having a system fail I'm settting up a new XP workstation. I've
installed my VS2008 SQL Server 2005 Client tools and I am able to connect
to
on SQL Server running on a Win2000 Server (shows up in browse for a list
of
servers on my LAN), but not to my laptop WinXP SQL Server 2000. On the
newer
system I attempted to use TCP/IP both Windows Auth and Server both failed
to
connect, TCP/IP is the only protocol enabled on the laptop for the SQL
2000
instance, the SQL 2005 has Shared memory & TCP/IP, however I have no
interest
in connecting to the 2005 instance.
I am able to connect to the laptop instance of SQL Server 2000 from the
Win2000 server using the QA so my best guess is that there's a
configuration
tweak I need to do to enable my WinXP system w/Client tools to connect to
my
laptop's instance of SQL Server 2000.
- References:
- SQLSMS - Cannot Connect SQL Server 2000
- From: JeffP->
- Re: SQLSMS - Cannot Connect SQL Server 2000
- From: Rick Byham, \(MSFT\)
- SQLSMS - Cannot Connect SQL Server 2000
- Prev by Date: Changing to Mixed Authentication
- Next by Date: RE: Database Mail error connecting to smtp server
- Previous by thread: Re: SQLSMS - Cannot Connect SQL Server 2000
- Next by thread: Database Mail error connecting to smtp server
- Index(es):
Relevant Pages
|
Loading