| Groups | Blog | Home |
sql server msde : Cannot connect to MSDE
Hello all,
I have two computers in LAN. Both computers are visible one to another. First computer has MSDE installed on it. Second cumputer runs application that needs to connect to MSDE installed on the first computer. The problem is that application installed on second computer cannot connect to MSDE and i cant figure out why is that so. The application running on first computer(the one that has MSDE installed on it) can connect to MSDE without any problems. MSDE is configured to use SQL Server authentication. Can anyone help me please ? Regards,
hi Tom,
[quoted text, click to view] Tom wrote: > Hello all, > > I have two computers in LAN. Both computers are visible > one to another. First computer has MSDE installed on it. > Second cumputer runs application that needs to connect to > MSDE installed on the first computer. The problem is that > application installed on second computer cannot connect to > MSDE and i cant figure out why is that so. > The application running on first computer(the one that > has MSDE installed on it) can connect to MSDE without any > problems. MSDE is configured to use SQL Server > authentication. Can anyone help me please ? > > Regards, > Tom MSDE installs by default disabling network protocols to prevent external mailcius attacks... you have to manually enable them, bot at install time providing the DISABLENETWORKPROTOCOLS=0 parameter to setup.exe boostrap installer and/or later using the Server Network Utility (svrnet.cn.exe) to enable the desired/required network protocol (usually TCP/IP) -- Andrea Montanari (Microsoft MVP - SQL Server) http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0 (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual interface) --------- remove DMO to reply
Hi Andrea,
I'm having the same problem. I am working in a peer-to-peer LAN (all XP stations) and have all my tools installed on one station (MSDE, Visual Studio, you great DbaMGR2k, Book Online, etc) and things are working fine, but I can't access SQL from the other stations. All the stations can see each others and share all other resources. - I used svrnetcn.exe to make certain TCP/IP protocol was installed, it was - I tried added named pipes too but it doesn't help - I logged in as Administrator but still have the problem Questions: - Do I need to install MSDE on all the stations? - Could Windows XP SP2 firewall be the problem? Thanks Richard [quoted text, click to view] Andrea Montanari wrote:
> hi Tom, > Tom wrote: > >>Hello all, >> >>I have two computers in LAN. Both computers are visible >>one to another. First computer has MSDE installed on it. >>Second cumputer runs application that needs to connect to >>MSDE installed on the first computer. The problem is that >>application installed on second computer cannot connect to >>MSDE and i cant figure out why is that so. >> The application running on first computer(the one that >>has MSDE installed on it) can connect to MSDE without any >>problems. MSDE is configured to use SQL Server >>authentication. Can anyone help me please ? >> >>Regards, >>Tom > > > MSDE installs by default disabling network protocols to prevent external > mailcius attacks... > you have to manually enable them, bot at install time providing the > DISABLENETWORKPROTOCOLS=0 > parameter to setup.exe boostrap installer and/or later using the Server > Network Utility (svrnet.cn.exe) to enable the desired/required network
Hi Andrea,
Thanks for the links [quoted text, click to view] > probably yes... > please have a look at http://support.microsoft.com/default.aspx?kbid=841249 > http://support.microsoft.com/default.aspx?scid=kb;[LN];841251 I tried what it said and I even tried disabling the XP SP2 firewall on both PCs but the second PC (the one without MSDE installed) still can't see the first PC (with MSDE and the databases). I tried using your utility, DbaMGR2k, on the second PC but when I try to connect, I get the error message, "429 - ActiveX component can't create object" I am new to MSDE and I am not sure if I need aliases, named pipes, special libaries etc. What I do have configured is TCP/IP protocol and I checked and it uses the default port 1433. I also only have one instance, the default, created during installation. I could try to install MSDE on a third PC with all the defaults and see what happens, but I'm fairly certain I didn't change anything from the recommended defaults during the initial installation. Any ideas why the other stations still can't see MSDE? Thanks. Richard Fagen [quoted text, click to view] >
> personally I always solved my troubles adding an exception to the firewall > for the related TCP/IP port both specifying a subnet range and/or defined > pc's IP ... if you can restrict the IP list your server will appreciate it > :D > for named instance the UDP 1434 port must be opened as well, if you do not > specify an ALIAS on all remote clients pointing to a static defined (and not
hi Richard,
[quoted text, click to view] Richard Fagen wrote: > Hi Andrea, > > I'm having the same problem. I am working in a peer-to-peer LAN (all > XP stations) and have all my tools installed on one station (MSDE, > Visual Studio, > > you great DbaMGR2k thank's :D [quoted text, click to view] > >, Book Online, etc) and things are > working > fine, but I can't access SQL from the other stations. All the > stations can see each others and share all other resources. > > - I used svrnetcn.exe to make certain TCP/IP protocol was installed, > it was > - I tried added named pipes too but it doesn't help > - I logged in as Administrator but still have the problem > > Questions: > - Do I need to install MSDE on all the stations? no, you don't [quoted text, click to view] > - Could Windows XP SP2 firewall be the problem? probably yes... please have a look at http://support.microsoft.com/default.aspx?kbid=841249 http://support.microsoft.com/default.aspx?scid=kb;[LN];841251 personally I always solved my troubles adding an exception to the firewall for the related TCP/IP port both specifying a subnet range and/or defined pc's IP ... if you can restrict the IP list your server will appreciate it :D for named instance the UDP 1434 port must be opened as well, if you do not specify an ALIAS on all remote clients pointing to a static defined (and not dinamically assigned) port -- Andrea Montanari (Microsoft MVP - SQL Server) http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0 (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual interface) --------- remove DMO to reply
hi Richard,
[quoted text, click to view] Richard Fagen wrote: > I tried what it said and I even tried disabling the XP SP2 firewall on > both PCs but the second PC (the one without MSDE installed) still > can't see the first PC (with MSDE and the databases). can you reach the MSDE installed pc from the remote client for standard sharing? can you ping it? can you telnet it, in the form c:\..\>telnet ComputerName 1433; if the screen becomes black you are in... then just type QUIT to exit.. [quoted text, click to view] > > I tried using your utility, DbaMGR2k, on the second PC but when I try > to connect, I get the error message, "429 - ActiveX component can't > create object" DbaMgr2k does not provide the SQL-DMO dependencies it relies on becouse of the presence several international localizations and service pack level.. in the application folder you can find the Depend2k.txt file which lists, in the SQL-DMO section, all the required files you can get from the MSDE installed pc and copy on the destination pc.. please fullfill the indicated hyerarchy and register via regsvr32 the required file (just 1) please feel free to privately contact me for any question or concern about the project, as long as for suggestions and feedback, as this is OT in this public newsgroup... [quoted text, click to view] > I am new to MSDE and I am not sure if I need aliases, named pipes, > special libaries etc. What I do have configured is TCP/IP protocol > and I checked and it uses the default port 1433. I also only have one > instance, the default, created during installation. that's ok.. the default instance listens on TCP/IP 1433 (if it has not been changed) and does not require an ALIAS nor the UDP 1434 port for the SQL Server Resolution Service to work as it is not needed.. [quoted text, click to view] > > Any ideas why the other stations still can't see MSDE? if all TCP/IP requirements and checks has been satisfied, I do think it's just a network problem.. please verify your connectivity other then SQL Server... again... for my personal tests I just referenced http://support.microsoft.com/default.aspx?kbid=841252 and worked like a charm... -- Andrea Montanari (Microsoft MVP - SQL Server) http://www.asql.biz/DbaMgr.shtm http://italy.mvps.org DbaMgr2k ver 0.10.0 - DbaMgr ver 0.56.0 (my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual interface) --------- remove DMO to reply
Don't see what you're looking for? Try a search.
|
June 2004
July 2004
August 2004
September 2004
October 2004
November 2004
December 2004
January 2005
February 2005
March 2005
April 2005
May 2005
June 2005
July 2005
August 2005
September 2005
October 2005
November 2005
December 2005
January 2006
February 2006
March 2006
April 2006
May 2006
June 2006
July 2006
August 2006
September 2006
October 2006
November 2006
December 2006
January 2007
February 2007
March 2007
April 2007
May 2007
June 2007
July 2007
August 2007
September 2007
October 2007
| home · blog · groups | Questions? Comments? Contact the dn |