MSDE remote connection failure

Hi all,

I installed a MSDE on a Windows XP SP2 and configured it for accepting remote connections. But It shows the "SQL Server doesnot exist or connection denied" message whenever I try to connect to this server. For more information I am adding more facts

* It is an MSDE and not a WMSDE
* Firewall is turned off
* Server process is listening on 0.0.0.0:1433
* TCP/IP and Named Pipes are enabled using server network utility
* LoginMode=2 is set for mixed mode authentication in the registry
* Tried restaring the Process and even windows after the changes.

Please help me !!

Thanks in advanceHi friends,
I got the issue fixed. :angel:

I dont know how it works but it worked.

On the client side; using the client network utility, I added an alias to my server.

My server's instance name was SLIMSHADY\SSIT and it was listening on 8001(I changed it thru the registry) in mixed mode authentication.

It wasted my 4-5 hours of playing with the registry and googling. The final attempt succeeded in which I created an alias to the server Indicating its exact port number and Instance name.

Then I tried connecting using this alias .... IT WORKED !!

I DONT KNOW HOW IT WORKS BUT IT WORKED IN MY CASE

HAPPY COMPUTING

MSDE remote connection failure

Hi all,

I installed a MSDE on a Windows XP SP2 and configured it for accepting remote connections. But It shows the "SQL Server doesnot exist or connection denied" message whenever I try to connect to this server. For more information I am adding more facts

* It is an MSDE and not a WMSDE
* Firewall is turned off
* Server process is listening on 0.0.0.0:1433
* TCP/IP and Named Pipes are enabled using server network utility
* LoginMode=2 is set for mixed mode authentication in the registry
* Tried restaring the Process and even windows after the changes.

Please help me !!

Thanks in advanceHi friends,
I got the issue fixed. :angel:

I dont know how it works but it worked.

On the client side; using the client network utility, I added an alias to my server.

My server's instance name was SLIMSHADY\SSIT and it was listening on 8001(I changed it thru the registry) in mixed mode authentication.

It wasted my 4-5 hours of playing with the registry and googling. The final attempt succeeded in which I created an alias to the server Indicating its exact port number and Instance name.

Then I tried connecting using this alias .... IT WORKED !!

I DONT KNOW HOW IT WORKS BUT IT WORKED IN MY CASE

HAPPY COMPUTING

MSDE installation/connection issues

I installed MSDE (sp3a) in a Windows 2000 server SP4. This is configured to
be a domain controller and (AD turned on). I can use MSDE webadmin to
access the database instance fine. I have a couple of problems.
1. MSSQLServerADHelper service does not startup.
System log message is:
The MSSQLServerADHelper service terminated with service-specific error
3221225572.
Corresponding Application log error is:
'0' is an invalid number of start up parameters. This service takes two
start up parameters.
2.Despite following the instructions in KB article: 840219 I still 'm not
able to login to MSDE using OSQL from a command prompt. Error message is:
Cr>osql -U domain\administrator -P xxxx
Login failed for user 'domain\administrator'. Reason: Not associated with a
trusted SQL Server connection.
Is something wrong with my syntax for the value for the -U parameter? I
restarted the SQL server and the agent services after following the steps in
840219.
Any suggestions appreciated.
hi,
"public.microsoft.com" <lakamsani AT gmail.com> ha scritto nel messaggio
news:%23kZ5Z$cbEHA.3684@.TK2MSFTNGP09.phx.gbl...
> I installed MSDE (sp3a) in a Windows 2000 server SP4. This is configured
to
> be a domain controller and (AD turned on). I can use MSDE webadmin to
> access the database instance fine. I have a couple of problems.
> 1. MSSQLServerADHelper service does not startup.
> System log message is:
> The MSSQLServerADHelper service terminated with service-specific error
> 3221225572.
please have a look at http://tinyurl.com/6qwgg

> 2.Despite following the instructions in KB article: 840219 I still 'm not
> able to login to MSDE using OSQL from a command prompt. Error message is:
> Cr>osql -U domain\administrator -P xxxx
> Login failed for user 'domain\administrator'. Reason: Not associated with
a
> trusted SQL Server connection.
> Is something wrong with my syntax for the value for the -U parameter? I
> restarted the SQL server and the agent services after following the steps
in
> 840219.
for trusted connections, you shoul'd pass the -E parameter (where -E
specifys a trusted connection using you actual WindowsNT login credential)
instead that providing SQL Server authenticated related credentials...
tipically
c:\>osql -E
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.8.0 - DbaMgr ver 0.54.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply