Dear all,
I'm using SQl Server 2K on a webserver and the sa password is "abcde". Using
this user name and password, and with ADO, I established our website.
Now the website is still working well,can input data,show data!!
But I cannot login to this SQL Server with "Enterprise Manager" or "Query
Analyzer" on the server. Either with sa or Windows-Authenticate. (I user the
administrator to login to the server).
I'm running EM and QA on the webserver(With administrator account), not on
the client PC.
The EM and QA can work well before.
One thing is, the webserver may be infected by virus of Spida Worm.
Currently, when I try to run EM or QA, then a long time waiting. Then told
me: connection failed,...
But the website system is still working well.
Please tell me how to run up the Enterprise Manager? Thanks a lot.
Hi
It is not a good idea to have SQL Server on an externally exposed server,
and it is always better to dedicate the server for a single use.
If you are connecting using ADO then you should be able to use the client
tools using the same login, check that you are using the same protocols.
John
"goldenshine" wrote:
> Dear all,
> I'm using SQl Server 2K on a webserver and the sa password is "abcde". Using
> this user name and password, and with ADO, I established our website.
> Now the website is still working well,can input data,show data!!
> But I cannot login to this SQL Server with "Enterprise Manager" or "Query
> Analyzer" on the server. Either with sa or Windows-Authenticate. (I user the
> administrator to login to the server).
> I'm running EM and QA on the webserver(With administrator account), not on
> the client PC.
> The EM and QA can work well before.
> One thing is, the webserver may be infected by virus of Spida Worm.
> Currently, when I try to run EM or QA, then a long time waiting. Then told
> me: connection failed,...
> But the website system is still working well.
> Please tell me how to run up the Enterprise Manager? Thanks a lot.
|||Thanks,John,
Can you please tell me how to check the protocols? Since the website(
Asp.net) can use ADO to connect SQL Server and works well, why
EnterpriseManager cannot?
Thanks
"John Bell" wrote:
[vbcol=seagreen]
> Hi
> It is not a good idea to have SQL Server on an externally exposed server,
> and it is always better to dedicate the server for a single use.
> If you are connecting using ADO then you should be able to use the client
> tools using the same login, check that you are using the same protocols.
> John
>
> "goldenshine" wrote:
|||Hi
Look in the client network configuration utility on the client and the
server network configuration utitlity on the server.
John
"goldenshine" <goldenshine@.discussions.microsoft.com> wrote in message
news:FA91D6BA-7F42-4BAA-A01C-969E63685059@.microsoft.com...[vbcol=seagreen]
> Thanks,John,
> Can you please tell me how to check the protocols? Since the website(
> Asp.net) can use ADO to connect SQL Server and works well, why
> EnterpriseManager cannot?
> Thanks
>
> "John Bell" wrote:
No comments:
Post a Comment