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 local host failure

Why would the localhost not install but rather our named instance will
install? We have an inconsistent problem with installations. Our app
depends on a named instance and a secondary app depends on local host
so we need both. However, systems that have previous installed,
uninstalled and try to reinstall the current app, only the local host
will install or the named instance will install, but not both. This
doesn't happen on all machines either. We encounter the usual errors
as seen in this group such as 'server not found', etc. and I can
usually get MSDE installed only if after I uninstall, I delete the MSDE
references in the registry. Yet I am baffled how MSDE would install
the named instance but not the local. This has primarily been occuring
on XP sp2 machines and all data resides on the client machine where
MSDE is installed.
Any suggestions?
Thanks.
hi,
Colleen wrote:
> Why would the localhost not install but rather our named instance will
> install? We have an inconsistent problem with installations. Our app
> depends on a named instance and a secondary app depends on local host
> so we need both. However, systems that have previous installed,
> uninstalled and try to reinstall the current app, only the local host
> will install or the named instance will install, but not both. This
> doesn't happen on all machines either. We encounter the usual errors
> as seen in this group such as 'server not found', etc. and I can
> usually get MSDE installed only if after I uninstall, I delete the
> MSDE references in the registry. Yet I am baffled how MSDE would
> install the named instance but not the local. This has primarily
> been occuring on XP sp2 machines and all data resides on the client
> machine where MSDE is installed.
just to test, I installed 2 additional named instances of MSDE (sp3 and sp4)
on a pc hosting 1 deafault instance of MSDE sp4...
and I am unable to reproduce the problem... of course, uninstalling an
instance requires you to manually clean the file system, or manually remove
all file system and windows registry entries...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.14.0 - DbaMgr ver 0.59.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply

MSDE is a COMPLETE MARKETING FAILURE as ZERO PEOPLE USE IT for anything, even development.

This summary is not available. Please click here to view the post.