Re: SSMS can't connect across LAN
- From: "Bill Cohagan" <cohagan@xxxxxxxxxxxxx>
- Date: Tue, 26 Feb 2008 11:51:33 -0600
Rick
Thanks for the pointer. I'll give it a look...
Bill
"Rick Byham, (MSFT)" <rickbyh@xxxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:3DC958C2-FC2D-44B3-AA06-C1BBCD69F836@xxxxxxxxxxxxxxxx
Try running through the tutorial in Books Online.
http://msdn2.microsoft.com/en-us/library/ms345318.aspx
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no
rights.
"Bill Cohagan" <cohagan@xxxxxxxxxxxxx> wrote in message
news:eVF7W5IeIHA.5552@xxxxxxxxxxxxxxxxxxxxxxx
Peter
When I went to Config Manager I discovered that named pipes protocol
wasn't enabled on the remote. So now I'm able to connect. Unfortunately
now the transfer fails with
errorcode=-1071636471 an ole db error has occurred
I've specified the NativeSQLClient for both source and destination dbs.
I've Googled this and found several other folks who encountered the
problem, but no solutions. Any ideas?
Bill
""Peter Yang[MSFT]"" <petery@xxxxxxxxxxxxxxxxxxxx> wrote in message
news:eTvHJqCeIHA.7396@xxxxxxxxxxxxxxxxxxxxxxxxx
Hello Bill,
Did you try to connect with TCPIP protocal other than Named pipes since
Named pipes may have been blocked by firewall.
You could check on server to make sure TCPIP is enabled via SQL Server
configuration manager.
Is the server a default instance or a named instance? You may want to
open
TCP 1433 port for default instance on server. For named instance,
usually
you need to open 1434 UDP port and TCP port used by that instance. You
may
want to refer to the following article:
INF: TCP Ports Needed for Communication to SQL Server Through a ...
http://support.microsoft.com/kb/287932
You could try to connect to remote server by using the TCPIP and port
name
like following in Management studio or SQLCMD:
TCP:servername (default instance)
TCP:servername\instancename (named instance)
TCP:servername,1433 (default instance)
TCP:servername\instancename,portnumber (named instance)
Please refer to the following link for more details about using
different
protocals and ports
How to: Connect to the Database Engine Using sqlcmd.exe
http://technet.microsoft.com/en-us/library/ms188247.aspx
If you have any update, please feel free to let's know. Thank you.
Best Regards,
Peter Yang
MCSE2000/2003, MCSA, MCDBA
Microsoft Online Community Support
==================================================
Get notification to my posts through email? Please refer to
http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx#notif
ications
<http://msdn.microsoft.com/subscriptions/managednewsgroups/default.aspx>.
Note: The MSDN Managed Newsgroup support offering is for non-urgent
issues
where an initial response from the community or a Microsoft Support
Engineer within 1 business day is acceptable. Please note that each
follow
up response may take approximately 2 business days as the support
professional working with you may need further investigation to reach
the
most efficient resolution. The offering is not appropriate for
situations
that require urgent, real-time or phone-based interactions or complex
project analysis and dump analysis issues. Issues of this nature are
best
handled working with a dedicated Microsoft Support Engineer by
contacting
Microsoft Customer Support Services (CSS) at
<http://msdn.microsoft.com/subscriptions/support/default.aspx>.
==================================================
This posting is provided "AS IS" with no warranties, and confers no
rights.
.
- References:
- SSMS can't connect across LAN
- From: Bill Cohagan
- RE: SSMS can't connect across LAN
- From: "Peter Yang[MSFT]"
- Re: SSMS can't connect across LAN
- From: Bill Cohagan
- Re: SSMS can't connect across LAN
- From: Rick Byham, \(MSFT\)
- SSMS can't connect across LAN
- Prev by Date: Re: SSMS can't connect across LAN
- Next by Date: Re: Copying tables with SQL Server 2005
- Previous by thread: Re: SSMS can't connect across LAN
- Next by thread: Re: SSMS can't connect across LAN
- Index(es):
Relevant Pages
|
