Intermittent connection

I am running SQL2000 on windows2003. I often connect to the database through
the SQL Server Enterprise Manager on a client machine to administer it. The
strange thing is sometimes I can connect to this database but other times c
annot. THe error message is
"SQL does not exist or not known to be running". I have checked the server s
tatus at the host terminal and it is running.
Anyone knows what's the problem for such intermitent connection? Network pro
b? SQL registration at the client side? ODBC setting?
Someone suggests that it may be because the host and the client are sitting
on different domain in the network. Is this true?Hi,
Due the problem situation, can you run a ping comand to the SQL Server
machine (Ping <ipaddress of sql server> ). If a request time out occurs
contact the "Network admin".
THis type of errors will come only if there is a slow network.
Thanks
Hari
MCDBA
"Tay" <Tay@.discussions.microsoft.com> wrote in message
news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> I am running SQL2000 on windows2003. I often connect to the database
through the SQL Server Enterprise Manager on a client machine to administer
it. The strange thing is sometimes I can connect to this database but other
times cannot. THe error message is "SQL does not exist or not known to be
running". I have checked the server status at the host terminal and it is
running.
> Anyone knows what's the problem for such intermitent connection? Network
prob? SQL registration at the client side? ODBC setting?
> Someone suggests that it may be because the host and the client are
sitting on different domain in the network. Is this true?|||Hi, Hari.
I can ping the sql server machine from the client terminal. But the client a
nd host are in different domain. Is this the problem?
Thanks.
Tay
"Hari Prasad" wrote:

> Hi,
> Due the problem situation, can you run a ping comand to the SQL Server
> machine (Ping <ipaddress of sql server> ). If a request time out occurs
> contact the "Network admin".
> THis type of errors will come only if there is a slow network.
>
> --
> Thanks
> Hari
> MCDBA
>
> "Tay" <Tay@.discussions.microsoft.com> wrote in message
> news:FD12B805-602B-447F-BB0F-181E032CA39E@.microsoft.com...
> through the SQL Server Enterprise Manager on a client machine to administe
r
> it. The strange thing is sometimes I can connect to this database but othe
r
> times cannot. THe error message is "SQL does not exist or not known to be
> running". I have checked the server status at the host terminal and it is
> running.
> prob? SQL registration at the client side? ODBC setting?
> sitting on different domain in the network. Is this true?
>
>|||HI,
If you have a Trust relation ship between both domains, then it should not
be a issue at all.
Thanks
Hari
MCDBA
"Tay" <Tay@.discussions.microsoft.com> wrote in message
news:90E8545E-343F-4061-8DA6-E5AACB0F385F@.microsoft.com...
> Hi, Hari.
> I can ping the sql server machine from the client terminal. But the client
and host are in different domain. Is this the problem?[vbcol=seagreen]
> Thanks.
> Tay
> "Hari Prasad" wrote:
>
administer[vbcol=seagreen]
other[vbcol=seagreen]
be[vbcol=seagreen]
is[vbcol=seagreen]
Network[vbcol=seagreen]|||hi
I just found out that both the host and the client did not join any domain b
ut in the same workgroup. I can successfully search for the sqlserver after
I login to a shared folder from my client terminal. It seems like the client
need to establish the netw
ork path to the host before it can find the sqlserver.
Any way to avoid logging in yet still can locate the sqlserver?
Thanks.
"Hari Prasad" wrote:

> HI,
> If you have a Trust relation ship between both domains, then it should not
> be a issue at all.
> --
> Thanks
> Hari
> MCDBA
> "Tay" <Tay@.discussions.microsoft.com> wrote in message
> news:90E8545E-343F-4061-8DA6-E5AACB0F385F@.microsoft.com...
> and host are in different domain. Is this the problem?
> administer
> other
> be
> is
> Network
>
>sql