connection error

Hi

I am getting following error while connecting in sql server. i have already disabled firewall, enabled remote connections using pipe and tcp and made sure the sql server and sql browser services are running.

but still the problem persists...can any help me ?

Named Pipes Provider: Could not open a connection to SQL Server [2].
Sqlcmd: Error: Microsoft SQL Native Client : An error has occurred while establi
shing a connection to the server. When connecting to SQL Server 2005, this failu
re may be caused by the fact that under the default settings SQL Server does not
allow remote connections..
Sqlcmd: Error: Microsoft SQL Native Client : Login timeout expired.

thanks in advance

Do you have a named instacne or a default one ? how are you connecting, you will have to provide some more information on your situation to make it easier forus to give you the right suggestions.

Jens K. Suessmeyer

http://www.sqlserver2005.de

Connecting to SQL Server over a VPN & through a router...

Hi All,
I have a NetGear combined wireless router / ADSL modem, and am
attempting to connect to SQL Server from my (wifi enabled) laptop, but
am getting a 'failed to create SSPI context' message (note that I'm
using Windows Authentication). I'm connected to my work LAN through a
SonicWall VPN. If I take the router out of the equation, I can connect
fine - even through the VPN.
Outlook also has no luck connecting - it appears that some aspect of
Windows Authentication is broken by the router being included in the
setup.
I can ping machines on my company LAN when connected through the
router, and can also connect to SQL server using the SS authentication
- so I'm not far away from being able to authenticate.
Any thoughts/help would be much appreciated.
Thanks,
Will (LemonSmasher)
Mmm... looks like I've 'solved' this. Having established the VPN
connection for the first time, I logged off of Windows, then logged
back on, reestablished the VPN connection and then authentication
worked. Must've been down to something being cached in my original
session - if anyone can shed light on this (or if its just a lucky
coincidence!), I'd be interested in hearing from you!
Will.
LemonSmas...@.hotmail.com wrote:
> Hi All,
> I have a NetGear combined wireless router / ADSL modem, and am
> attempting to connect to SQL Server from my (wifi enabled) laptop, but
> am getting a 'failed to create SSPI context' message (note that I'm
> using Windows Authentication). I'm connected to my work LAN through a
> SonicWall VPN. If I take the router out of the equation, I can connect
> fine - even through the VPN.
> Outlook also has no luck connecting - it appears that some aspect of
> Windows Authentication is broken by the router being included in the
> setup.
> I can ping machines on my company LAN when connected through the
> router, and can also connect to SQL server using the SS authentication
> - so I'm not far away from being able to authenticate.
> Any thoughts/help would be much appreciated.
> Thanks,
> Will (LemonSmasher)

Connecting to SQL Server over a VPN & through a router...

Hi All,
I have a NetGear combined wireless router / ADSL modem, and am
attempting to connect to SQL Server from my (wifi enabled) laptop, but
am getting a 'failed to create SSPI context' message (note that I'm
using Windows Authentication). I'm connected to my work LAN through a
SonicWall VPN. If I take the router out of the equation, I can connect
fine - even through the VPN.
Outlook also has no luck connecting - it appears that some aspect of
Windows Authentication is broken by the router being included in the
setup.
I can ping machines on my company LAN when connected through the
router, and can also connect to SQL server using the SS authentication
- so I'm not far away from being able to authenticate.
Any thoughts/help would be much appreciated.
Thanks,
Will (LemonSmasher)Mmm... looks like I've 'solved' this. Having established the VPN
connection for the first time, I logged off of Windows, then logged
back on, reestablished the VPN connection and then authentication
worked. Must've been down to something being cached in my original
session - if anyone can shed light on this (or if its just a lucky
coincidence!), I'd be interested in hearing from you!
Will.
LemonSmas...@.hotmail.com wrote:
> Hi All,
> I have a NetGear combined wireless router / ADSL modem, and am
> attempting to connect to SQL Server from my (wifi enabled) laptop, but
> am getting a 'failed to create SSPI context' message (note that I'm
> using Windows Authentication). I'm connected to my work LAN through a
> SonicWall VPN. If I take the router out of the equation, I can connect
> fine - even through the VPN.
> Outlook also has no luck connecting - it appears that some aspect of
> Windows Authentication is broken by the router being included in the
> setup.
> I can ping machines on my company LAN when connected through the
> router, and can also connect to SQL server using the SS authentication
> - so I'm not far away from being able to authenticate.
> Any thoughts/help would be much appreciated.
> Thanks,
> Will (LemonSmasher)

Connecting to SQL Server 2005 over VPN Not working

I am having trouble connecting to SQL Server 2005 from my home via VPN
connection to my office. I have enabled remote connections on the
server. I can actually connect to my local SQL Server instance from
the Server machine while connected to the VPN but not the other way
around. I can browse shared folders from the Server machine so my vpn
connection is good. Other machines in the office can remotely connect
to the SQL Server instance on the server machine.
Is there some setting on the server, such as somewhere in RRAS, that I
need to configure to allow me to connect?
FYI: I am using SQL Authentication
ThanksHi
"chack.busedge@.gmail.com" wrote:

> I am having trouble connecting to SQL Server 2005 from my home via VPN
> connection to my office. I have enabled remote connections on the
> server. I can actually connect to my local SQL Server instance from
> the Server machine while connected to the VPN but not the other way
> around. I can browse shared folders from the Server machine so my vpn
> connection is good. Other machines in the office can remotely connect
> to the SQL Server instance on the server machine.
> Is there some setting on the server, such as somewhere in RRAS, that I
> need to configure to allow me to connect?
> FYI: I am using SQL Authentication
> Thanks
>
Check out http://support.microsoft.com/kb/287932 on the ports that you will
need to have access to for the connection. Have you tried terminal services
or Remote desktop to access the server?
John|||On Jun 28, 12:32 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
>
>
> "chack.buse...@.gmail.com" wrote:
>
>
>
> Check outhttp://support.microsoft.com/kb/287932on the ports that you will
> need to have access to for the connection. Have you tried terminal service
s
> or Remote desktop to access the server?
> John- Hide quoted text -
> - Show quoted text -
The VPN was configured using the RRAS console. Is there something I
need to configure there to allow port 1433 access via VPN?
Yes, I can remote desktop into the server. That's how I am
configuring the VPN.
Thanks|||On Jun 28, 1:39 pm, chack.buse...@.gmail.com wrote:
> On Jun 28, 12:32 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
>
>
>
>
>
>
>
>
> TheVPNwas configured using the RRAS console. Is there something I
> need to configure there to allow port 1433 access viaVPN?
> Yes, I can remote desktop into theserver. That's how I am
> configuring theVPN.
> Thanks- Hide quoted text -
> - Show quoted text -
Ok, I finally got something to work. I was reviewing this article
http://support.microsoft.com/kb/265808 when I found the IPAll Dynamic
Ports value to be 1033. On a whim I decided to set my server name
value for my connection to...
SERVER\INSTANCENAME,1033
And voila, it freeking worked. I don't know why, but at this point I
don't care. I am thrilled to have a connection that I can use at
home. I sure hope this helps out someone else in the future.|||Hi
"chack.busedge@.gmail.com" wrote:

> On Jun 28, 1:39 pm, chack.buse...@.gmail.com wrote:
> Ok, I finally got something to work. I was reviewing this article
> http://support.microsoft.com/kb/265808 when I found the IPAll Dynamic
> Ports value to be 1033. On a whim I decided to set my server name
> value for my connection to...
> SERVER\INSTANCENAME,1033
> And voila, it freeking worked. I don't know why, but at this point I
> don't care. I am thrilled to have a connection that I can use at
> home. I sure hope this helps out someone else in the future.
>
You had not said that you had a named instance of SQL Server!! By default
that will use a dynamic port instead of 1433 see
http://msdn2.microsoft.com/en-us/library/ms177440.aspx You have forced the
server to use a specific port (which seems to be open!!)
Ports from 1024 through 49151 are IANA registered ports, and 1033 is
registered for netinfo. IANA recommend that dynamic or Private Ports from
49152 through 65535 are used.
John

Connecting to SQL Server 2005 over VPN Not working

I am having trouble connecting to SQL Server 2005 from my home via VPN
connection to my office. I have enabled remote connections on the
server. I can actually connect to my local SQL Server instance from
the Server machine while connected to the VPN but not the other way
around. I can browse shared folders from the Server machine so my vpn
connection is good. Other machines in the office can remotely connect
to the SQL Server instance on the server machine.
Is there some setting on the server, such as somewhere in RRAS, that I
need to configure to allow me to connect?
FYI: I am using SQL Authentication
Thanks
Hi
"chack.busedge@.gmail.com" wrote:

> I am having trouble connecting to SQL Server 2005 from my home via VPN
> connection to my office. I have enabled remote connections on the
> server. I can actually connect to my local SQL Server instance from
> the Server machine while connected to the VPN but not the other way
> around. I can browse shared folders from the Server machine so my vpn
> connection is good. Other machines in the office can remotely connect
> to the SQL Server instance on the server machine.
> Is there some setting on the server, such as somewhere in RRAS, that I
> need to configure to allow me to connect?
> FYI: I am using SQL Authentication
> Thanks
>
Check out http://support.microsoft.com/kb/287932 on the ports that you will
need to have access to for the connection. Have you tried terminal services
or Remote desktop to access the server?
John
|||On Jun 28, 12:32 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
>
>
> "chack.buse...@.gmail.com" wrote:
>
>
> Check outhttp://support.microsoft.com/kb/287932on the ports that you will
> need to have access to for the connection. Have you tried terminal services
> or Remote desktop to access the server?
> John- Hide quoted text -
> - Show quoted text -
The VPN was configured using the RRAS console. Is there something I
need to configure there to allow port 1433 access via VPN?
Yes, I can remote desktop into the server. That's how I am
configuring the VPN.
Thanks
|||On Jun 28, 1:39 pm, chack.buse...@.gmail.com wrote:
> On Jun 28, 12:32 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
>
>
>
>
> TheVPNwas configured using the RRAS console. Is there something I
> need to configure there to allow port 1433 access viaVPN?
> Yes, I can remote desktop into theserver. That's how I am
> configuring theVPN.
> Thanks- Hide quoted text -
> - Show quoted text -
Ok, I finally got something to work. I was reviewing this article
http://support.microsoft.com/kb/265808 when I found the IPAll Dynamic
Ports value to be 1033. On a whim I decided to set my server name
value for my connection to...
SERVER\INSTANCENAME,1033
And voila, it freeking worked. I don't know why, but at this point I
don't care. I am thrilled to have a connection that I can use at
home. I sure hope this helps out someone else in the future.
|||Hi
"chack.busedge@.gmail.com" wrote:

> On Jun 28, 1:39 pm, chack.buse...@.gmail.com wrote:
> Ok, I finally got something to work. I was reviewing this article
> http://support.microsoft.com/kb/265808 when I found the IPAll Dynamic
> Ports value to be 1033. On a whim I decided to set my server name
> value for my connection to...
> SERVER\INSTANCENAME,1033
> And voila, it freeking worked. I don't know why, but at this point I
> don't care. I am thrilled to have a connection that I can use at
> home. I sure hope this helps out someone else in the future.
>
You had not said that you had a named instance of SQL Server!! By default
that will use a dynamic port instead of 1433 see
http://msdn2.microsoft.com/en-us/library/ms177440.aspx You have forced the
server to use a specific port (which seems to be open!!)
Ports from 1024 through 49151 are IANA registered ports, and 1033 is
registered for netinfo. IANA recommend that dynamic or Private Ports from
49152 through 65535 are used.
John

Connecting to SQL Server 2005 over VPN Not working

I am having trouble connecting to SQL Server 2005 from my home via VPN
connection to my office. I have enabled remote connections on the
server. I can actually connect to my local SQL Server instance from
the Server machine while connected to the VPN but not the other way
around. I can browse shared folders from the Server machine so my vpn
connection is good. Other machines in the office can remotely connect
to the SQL Server instance on the server machine.
Is there some setting on the server, such as somewhere in RRAS, that I
need to configure to allow me to connect?
FYI: I am using SQL Authentication
ThanksHi
"chack.busedge@.gmail.com" wrote:
> I am having trouble connecting to SQL Server 2005 from my home via VPN
> connection to my office. I have enabled remote connections on the
> server. I can actually connect to my local SQL Server instance from
> the Server machine while connected to the VPN but not the other way
> around. I can browse shared folders from the Server machine so my vpn
> connection is good. Other machines in the office can remotely connect
> to the SQL Server instance on the server machine.
> Is there some setting on the server, such as somewhere in RRAS, that I
> need to configure to allow me to connect?
> FYI: I am using SQL Authentication
> Thanks
>
Check out http://support.microsoft.com/kb/287932 on the ports that you will
need to have access to for the connection. Have you tried terminal services
or Remote desktop to access the server?
John|||On Jun 28, 12:32 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> Hi
>
>
> "chack.buse...@.gmail.com" wrote:
> > I am having trouble connecting to SQL Server 2005 from my home via VPN
> > connection to my office. I have enabled remote connections on the
> > server. I can actually connect to my local SQL Server instance from
> > the Server machine while connected to the VPN but not the other way
> > around. I can browse shared folders from the Server machine so my vpn
> > connection is good. Other machines in the office can remotely connect
> > to the SQL Server instance on the server machine.
> > Is there some setting on the server, such as somewhere in RRAS, that I
> > need to configure to allow me to connect?
> > FYI: I am using SQL Authentication
> > Thanks
> Check outhttp://support.microsoft.com/kb/287932on the ports that you will
> need to have access to for the connection. Have you tried terminal services
> or Remote desktop to access the server?
> John- Hide quoted text -
> - Show quoted text -
The VPN was configured using the RRAS console. Is there something I
need to configure there to allow port 1433 access via VPN?
Yes, I can remote desktop into the server. That's how I am
configuring the VPN.
Thanks|||On Jun 28, 1:39 pm, chack.buse...@.gmail.com wrote:
> On Jun 28, 12:32 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
>
>
> > Hi
> > "chack.buse...@.gmail.com" wrote:
> > > I am having trouble connecting toSQLServer2005from my home viaVPN
> > > connection to my office. I have enabled remote connections on the
> > >server. I can actually connect to my localSQLServerinstance from
> > > theServermachine while connected to theVPNbut not the other way
> > > around. I can browse shared folders from theServermachine so myvpn
> > > connection is good. Other machines in the office can remotely connect
> > > to theSQLServerinstance on theservermachine.
> > > Is there some setting on theserver, such as somewhere in RRAS, that I
> > > need to configure to allow me to connect?
> > > FYI: I am usingSQLAuthentication
> > > Thanks
> > Check outhttp://support.microsoft.com/kb/287932onthe ports that you will
> > need to have access to for the connection. Have you tried terminal services
> > or Remote desktop to access theserver?
> > John- Hide quoted text -
> > - Show quoted text -
> TheVPNwas configured using the RRAS console. Is there something I
> need to configure there to allow port 1433 access viaVPN?
> Yes, I can remote desktop into theserver. That's how I am
> configuring theVPN.
> Thanks- Hide quoted text -
> - Show quoted text -
Ok, I finally got something to work. I was reviewing this article
http://support.microsoft.com/kb/265808 when I found the IPAll Dynamic
Ports value to be 1033. On a whim I decided to set my server name
value for my connection to...
SERVER\INSTANCENAME,1033
And voila, it freeking worked. I don't know why, but at this point I
don't care. I am thrilled to have a connection that I can use at
home. I sure hope this helps out someone else in the future.|||Hi
"chack.busedge@.gmail.com" wrote:
> On Jun 28, 1:39 pm, chack.buse...@.gmail.com wrote:
> > On Jun 28, 12:32 pm, John Bell <jbellnewspo...@.hotmail.com> wrote:
> >
> >
> >
> >
> >
> > > Hi
> >
> > > "chack.buse...@.gmail.com" wrote:
> > > > I am having trouble connecting toSQLServer2005from my home viaVPN
> > > > connection to my office. I have enabled remote connections on the
> > > >server. I can actually connect to my localSQLServerinstance from
> > > > theServermachine while connected to theVPNbut not the other way
> > > > around. I can browse shared folders from theServermachine so myvpn
> > > > connection is good. Other machines in the office can remotely connect
> > > > to theSQLServerinstance on theservermachine.
> >
> > > > Is there some setting on theserver, such as somewhere in RRAS, that I
> > > > need to configure to allow me to connect?
> >
> > > > FYI: I am usingSQLAuthentication
> >
> > > > Thanks
> >
> > > Check outhttp://support.microsoft.com/kb/287932onthe ports that you will
> > > need to have access to for the connection. Have you tried terminal services
> > > or Remote desktop to access theserver?
> >
> > > John- Hide quoted text -
> >
> > > - Show quoted text -
> >
> > TheVPNwas configured using the RRAS console. Is there something I
> > need to configure there to allow port 1433 access viaVPN?
> >
> > Yes, I can remote desktop into theserver. That's how I am
> > configuring theVPN.
> >
> > Thanks- Hide quoted text -
> >
> > - Show quoted text -
> Ok, I finally got something to work. I was reviewing this article
> http://support.microsoft.com/kb/265808 when I found the IPAll Dynamic
> Ports value to be 1033. On a whim I decided to set my server name
> value for my connection to...
> SERVER\INSTANCENAME,1033
> And voila, it freeking worked. I don't know why, but at this point I
> don't care. I am thrilled to have a connection that I can use at
> home. I sure hope this helps out someone else in the future.
>
You had not said that you had a named instance of SQL Server!! By default
that will use a dynamic port instead of 1433 see
http://msdn2.microsoft.com/en-us/library/ms177440.aspx You have forced the
server to use a specific port (which seems to be open!!)
Ports from 1024 through 49151 are IANA registered ports, and 1033 is
registered for netinfo. IANA recommend that dynamic or Private Ports from
49152 through 65535 are used.
John