Re: SQL 2000, Named Pipes and Windows 2003 Standard

Hi John,
I am not an expert on Named Pipes (well actually I am somewhat, but not
using it as an SQL client) but had a similar problem when trying to use
Named Pipes on new XP SP2 Pro machines. For 9 months I tore my hair out
trying to figure out why Named Pipes would work between our controller
(embedded NT using the named pipes API) and our Win2K boxes and older WinXP
(upgraded to SP2) but not on new XP Pro machines. As it turns out, the new
machines come with XP Pro and SP2 installed and Simple File Sharing enabled.
Once disabled, Named Pipes worked.
To disable SFS, go into Win Explorer, Tools, Folder Options, View and scroll
down to bottom.
Hope this helps.
Larry

ps- I am actually in the NG to find more information in setting up our
controller to talk directly to the SQL server via Named Pipes. Presently I
am catching the data on the Front End (client machine) and writing it to the
database. I want the back-end (versa-logic controller) to write directly to
the server via Named Pipes.



"Josh Danko" <josh@xxxxxxxxxxx> wrote in message
news:%23yEJ3CjoGHA.220@xxxxxxxxxxxxxxxxxxxxxxx
Just to clarify. I can access net use \\sqlserver\IPC$ so windows
authentication doesn't seem to be the issue. I went through the
makepipe/readpipe and that all works fine. Also, everytime i try to
connect to the SQL using named pipes i get a security audit log. Although
it doesn't say much.

Josh

"Josh Danko" <josh@xxxxxxxxxxx> wrote in message
news:%23ouYANioGHA.4036@xxxxxxxxxxxxxxxxxxxxxxx
We had a problem in the past where changing from TCP/IP to Named Pipes
fixed a SQL Connection timeout that happened every so often. Well, now
we seperated the Web server and SQL Server onto our new Dell Blade
systems which are pretty fast (faster than what it used to be on).
However, I cannot get named pipes to work. It fails to connect but
TCP/IP works fine. We are using TCP/IP now, but I am getting a few
timeouts every day just like before (just not as many). So, I disabled
the firewall on both machines for the private network it uses to connect.
Windows 2003 is fully updated and SQL2000 is updated to SP4. I cannot
figure out why Named Pipes will not work. I even tried from an XPSP2
laptop I brought it in and it won't connect using named pipes either. Is
there any kind of patch, dll or something I need to do to allow named
pipes to work over a small LAN? The servers are connected using a direct
Gigabit connection isolated to only the two servers on the same network
with all firewalls disabled.





.

Relevant Pages

  • Re: Kann das SQL Server Express Management Studio nicht öffnen.
    ... Herstellen einer Verbindung mit SQL Server 2005 kann dieser Fehler ... kam die Ausschrift mit "Named Pipes" ...
    (microsoft.public.de.german.entwickler.dotnet.datenbank)
  • Re: SQL 2000, Named Pipes and Windows 2003 Standard
    ... Named Pipes on new XP SP2 Pro machines. ... WinXP but not on new XP Pro machines. ... controller to talk directly to the SQL server via Named Pipes. ...
    (microsoft.public.sqlserver.connect)
  • Re: Cant connect to SQL
    ... You're still trying to use Named Pipes. ... Use both Client and Server Network ... Hello, the SQL Server 2000 installation uses Mixed authentication, SQL and ... "Client unable to establish connection. ...
    (microsoft.public.sqlserver.server)
  • Re: Web Server 2003 > Install SQL Agent
    ... the server has named pipes enabled too. ... Mike Epprecht, Microsoft SQL Server MVP ...
    (microsoft.public.windows.server.general)
  • Re: Web Server 2003 > Install SQL Agent
    ... the server has named pipes enabled too. ... Mike Epprecht, Microsoft SQL Server MVP ...
    (microsoft.public.sqlserver.server)
Loading