I'm not sure if i'm asking in the right place but I've to start some where. Recently our company got our hands on the Windows 2003 Server Standard Edition and also SQL Server 2000 Standard Edition. We've tried to install both of these onto a development server and the autorun on the SQL Server 2000 CD prompts that it will not run with any service pack below service pack 2. So we installed the database server along with service packs 1, 2 and 3 into the server. Running the database server on the local machine proves that nothing is wrong where everything can run on the enterprise manager and query analyzer. But when we turn to the client machines and tried to register the SQL Server instance with enterprise manager on the client machines, it just returns "Server non-existing or access denied" error, even when the password and username is correct (user logins set at the development server). Did we miss anything that we need to set or have we done the whole thing wrong? Can anybody help?Are the clients able to access the server in other ways such as ping or smb?
If not, it might be the built-in firewall in 2003. You can find it by going
into the properties of the network connection.
"Chris" <honchein.choi@.newera.edu.my> wrote in message
news:514C4401-60B6-4D19-9605-34E2A5D01BB9@.microsoft.com...
> I'm not sure if i'm asking in the right place but I've to start some
where. Recently our company got our hands on the Windows 2003 Server
Standard Edition and also SQL Server 2000 Standard Edition. We've tried to
install both of these onto a development server and the autorun on the SQL
Server 2000 CD prompts that it will not run with any service pack below
service pack 2. So we installed the database server along with service packs
1, 2 and 3 into the server. Running the database server on the local machine
proves that nothing is wrong where everything can run on the enterprise
manager and query analyzer. But when we turn to the client machines and
tried to register the SQL Server instance with enterprise manager on the
client machines, it just returns "Server non-existing or access denied"
error, even when the password and username is correct (user logins set at
the development server). Did we miss anything that we need to set or have we
done the whole thing wrong? Can anybody help?|||I'm sure that all clients can't access to the database server, enterprise manager, query analyzer, odbc connections, etc. i've checked the properties of the network connection and the firewall wasn't activated automatically and i can ping the server through tcp/ip protocol. that's y i dunno wut's wrong here. any ideas
-- Johan wrote: --
Are the clients able to access the server in other ways such as ping or smb
If not, it might be the built-in firewall in 2003. You can find it by goin
into the properties of the network connection
"Chris" <honchein.choi@.newera.edu.my> wrote in messag
news:514C4401-60B6-4D19-9605-34E2A5D01BB9@.microsoft.com..
> I'm not sure if i'm asking in the right place but I've to start som
where. Recently our company got our hands on the Windows 2003 Serve
Standard Edition and also SQL Server 2000 Standard Edition. We've tried t
install both of these onto a development server and the autorun on the SQ
Server 2000 CD prompts that it will not run with any service pack belo
service pack 2. So we installed the database server along with service pack
1, 2 and 3 into the server. Running the database server on the local machin
proves that nothing is wrong where everything can run on the enterpris
manager and query analyzer. But when we turn to the client machines an
tried to register the SQL Server instance with enterprise manager on th
client machines, it just returns "Server non-existing or access denied
error, even when the password and username is correct (user logins set a
the development server). Did we miss anything that we need to set or have w
done the whole thing wrong? Can anybody help?
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment