Hello --



If this is off-track, please suggest a group in which to post it.



I am using SQL Server 2000 (Management Console SP3).



I receive this error after clicking (LOCAL) (Windows NT), after

connecting to my ISP using dialup with a TRENDnet TFM-560U USB modem.



It happens whether or not the modem is online after a connection has

once been made.  It does not happen if I start SQL Server after a cold boot.



TRENDnet says it is an operating system problem and refers me to article

http://support.microsoft.com/?id=811889



How can it be an operating system problem if a cold boot results in no

error message?



Does anyone have an idea why this is happening?



Thanks for any help.



Larry Mehl

I'm not sure why it's trying to use TCP/IP to connect to your local instance

(generally it would use Shared Memory which shouldn't cause an SSPI error)

but it's most likely a DNS issue caused by you being online. To workaround

this, set up a client alias to you local instance using Named Pipes as this

is not affected by this error. Goto Start>Run and type cliconfg and hit

enter. This will bring up the client network utility. Select the Alias tab

and click Add. Make sure Named Pipes is selected in the Network libraries

radio button list on the left and then type the name of your PC into the

Server Alias textbox and click OK and then Apply.



--

HTH



Jasper Smith (SQL Server MVP)

http://www.sqldbatips.com

I support PASS - the definitive, global

community for SQL Server professionals -

http://www.sqlpass.org



"L Mehl" <mehlSCRATCHTHIS@cyvest.com> wrote in message

news:430CA739.9010801@cyvest.com...

> Hello --

>

> If this is off-track, please suggest a group in which to post it.

>

> I am using SQL Server 2000 (Management Console SP3).

>

> I receive this error after clicking (LOCAL) (Windows NT), after connecting

> to my ISP using dialup with a TRENDnet TFM-560U USB modem.

>

> It happens whether or not the modem is online after a connection has once

> been made.  It does not happen if I start SQL Server after a cold boot.

>

> TRENDnet says it is an operating system problem and refers me to article

> http://support.microsoft.com/?id=811889

>

> How can it be an operating system problem if a cold boot results in no

> error message?

>

> Does anyone have an idea why this is happening?

>

> Thanks for any help.

>

> Larry Mehl

Hello



I had this problem but it's have realtion with the system date. when the

system date is different from the database server, this message occurs.







"L Mehl" wrote:



> Hello --

>

> If this is off-track, please suggest a group in which to post it.

>

> I am using SQL Server 2000 (Management Console SP3).

>

> I receive this error after clicking (LOCAL) (Windows NT), after

> connecting to my ISP using dialup with a TRENDnet TFM-560U USB modem.

>

> It happens whether or not the modem is online after a connection has

> once been made.  It does not happen if I start SQL Server after a cold boot.

>

> TRENDnet says it is an operating system problem and refers me to article

> http://support.microsoft.com/?id=811889

>

> How can it be an operating system problem if a cold boot results in no

> error message?

>

> Does anyone have an idea why this is happening?

>

> Thanks for any help.

>

> Larry Mehl

>

Hello



I had this problem but it's have realtion with the system date. when the

system date is different from the database server, this message occurs.







"L Mehl" wrote:



> Hello --

>

> If this is off-track, please suggest a group in which to post it.

>

> I am using SQL Server 2000 (Management Console SP3).

>

> I receive this error after clicking (LOCAL) (Windows NT), after

> connecting to my ISP using dialup with a TRENDnet TFM-560U USB modem.

>

> It happens whether or not the modem is online after a connection has

> once been made.  It does not happen if I start SQL Server after a cold boot.

>

> TRENDnet says it is an operating system problem and refers me to article

> http://support.microsoft.com/?id=811889

>

> How can it be an operating system problem if a cold boot results in no

> error message?

>

> Does anyone have an idea why this is happening?

>

> Thanks for any help.

>

> Larry Mehl

>

Thanks Jasper.



I will try your suggestion.



Do you have any idea why the error recently appeared, after connecting the

same way for a long time?



Larry



"Jasper Smith" <jasper_smith9@hotmail.com> wrote in message

news:uuzUWFPqFHA.324@TK2MSFTNGP10.phx.gbl...

> I'm not sure why it's trying to use TCP/IP to connect to your local

instance

> (generally it would use Shared Memory which shouldn't cause an SSPI error)

> but it's most likely a DNS issue caused by you being online. To workaround

> this, set up a client alias to you local instance using Named Pipes as

this[vbcol=seagreen]

> is not affected by this error. Goto Start>Run and type cliconfg and hit

> enter. This will bring up the client network utility. Select the Alias tab

> and click Add. Make sure Named Pipes is selected in the Network libraries

> radio button list on the left and then type the name of your PC into the

> Server Alias textbox and click OK and then Apply.

>

> --

> HTH

>

> Jasper Smith (SQL Server MVP)

> http://www.sqldbatips.com

> I support PASS - the definitive, global

> community for SQL Server professionals -

> http://www.sqlpass.org

>

> "L Mehl" <mehlSCRATCHTHIS@cyvest.com> wrote in message

> news:430CA739.9010801@cyvest.com... 

connecting[vbcol=seagreen] 

once 

>

>

Thanks Julio  --



Can you tell me how to bring the dates into synch?



Larry



"Julio Cesar Silva" <Julio Cesar Silva@discussions.microsoft.com> wrote in

message news:885A5327-4327-4618-B906-34FBB0FA9FD3@microsoft.com...[vbcol=seagreen]

> Hello

>

> I had this problem but it's have realtion with the system date. when the

> system date is different from the database server, this message occurs.

>

>

>

> "L Mehl" wrote:

> 

boot.[vbcol=seagreen] 

Jasper --



I'm a real newbie at this.



Will setting up a client alias to my local instance affect the db and VB

application when I put it on another user's machine?



Thanks.



Larry



"Jasper Smith" <jasper_smith9@hotmail.com> wrote in message

news:uuzUWFPqFHA.324@TK2MSFTNGP10.phx.gbl...

> I'm not sure why it's trying to use TCP/IP to connect to your local

instance

> (generally it would use Shared Memory which shouldn't cause an SSPI error)

> but it's most likely a DNS issue caused by you being online. To workaround

> this, set up a client alias to you local instance using Named Pipes as

this[vbcol=seagreen]

> is not affected by this error. Goto Start>Run and type cliconfg and hit

> enter. This will bring up the client network utility. Select the Alias tab

> and click Add. Make sure Named Pipes is selected in the Network libraries

> radio button list on the left and then type the name of your PC into the

> Server Alias textbox and click OK and then Apply.

>

> --

> HTH

>

> Jasper Smith (SQL Server MVP)

> http://www.sqldbatips.com

> I support PASS - the definitive, global

> community for SQL Server professionals -

> http://www.sqlpass.org

>

> "L Mehl" <mehlSCRATCHTHIS@cyvest.com> wrote in message

> news:430CA739.9010801@cyvest.com... 

connecting[vbcol=seagreen] 

once 

>

>

Jasper --



In reading some of your other postings on this topic, I see:

"We tend to find they cause more trouble than they're worth and I'd actually

advise you delete any SPN's for the server/service account unless you

specifically need to be able to delegate.

SPI errors are generally SPN or DNS related."



Deleting sounds good to me (I don't know what "delegate" means)



Running setspn to get a list of the registered SPNs, each of these:

Setspn -L SLMEHL

Setspn -L LOCALHOST

Setspn -L LOCAL

resulted in

"Cannot find account ..."



Can you tell me how to find what accounts I have, so that I can use

Setspn -D ...  ?



Thanks for any further help.



Larry





"Jasper Smith" <jasper_smith9@hotmail.com> wrote in message

news:uuzUWFPqFHA.324@TK2MSFTNGP10.phx.gbl...

> I'm not sure why it's trying to use TCP/IP to connect to your local

instance

> (generally it would use Shared Memory which shouldn't cause an SSPI error)

> but it's most likely a DNS issue caused by you being online. To workaround

> this, set up a client alias to you local instance using Named Pipes as

this[vbcol=seagreen]

> is not affected by this error. Goto Start>Run and type cliconfg and hit

> enter. This will bring up the client network utility. Select the Alias tab

> and click Add. Make sure Named Pipes is selected in the Network libraries

> radio button list on the left and then type the name of your PC into the

> Server Alias textbox and click OK and then Apply.

>

> --

> HTH

>

> Jasper Smith (SQL Server MVP)

> http://www.sqldbatips.com

> I support PASS - the definitive, global

> community for SQL Server professionals -

> http://www.sqlpass.org

>

> "L Mehl" <mehlSCRATCHTHIS@cyvest.com> wrote in message

> news:430CA739.9010801@cyvest.com... 

connecting[vbcol=seagreen] 

once 

>

>