|
|
Posted by John Bell on 09/09/06 06:45
Hi
To add to my own post...
Check out the connectivity using SQLCMD and SQL Management Studio to see if
there are any issues and see if you have the same problems on the server
itself.
John
"John Bell" <jbellnewsposts@hotmail.com> wrote in message
news:4502613e$0$27307$db0fefd9@news.zen.co.uk...
> Hi Rick
>
> This sounds like you are having problems connecting to the AD to
> authenticate the user. It could be a general network problem. Have you
> seen if this is any better with SQL Server authentication? Other things to
> check may be disc space on the server and workstation and also
> fragmentation of the discs as well as the network hardware.
>
> John
> "Rico" <me@you.com> wrote in message
> news:fgZLg.516456$iF6.129615@pd7tw2no...
>> Hello,
>>
>> I have a Win2K3 Server with SS2005 developers edition. I am working on a
>> Windows XP Pro workstation which has SQL Server 2000 installed as well as
>> the SQL Native Client. I'm using an MS Access ADP to connect to the
>> server and for some reason it's extremely slow, even to the point of
>> throwing time out errors and "can't generate SSPI context" messages.
>> I've hit the MS website and found info on the SSPI error, but none of the
>> items that generate the error apply to my situation. I've tried using
>> the surface area manager to change the connection to name pipes, name
>> pipes and tcpip etc, but no luck.
>>
>> Is there anything I should be looking at or any known issues that would
>> affect this kind of performance?
>>
>> Thanks!
>> Rick
>>
>>
>
>
Navigation:
[Reply to this message]
|