One client machine gets a connection error

Which talks about Named Pipes.
We're not using Named Pipes, we're using TCP/IP.
All of the four other machines work...why not this one.
Note. It's a machine that has been reformatted and programs reinstalled.
But my program does nothing special other than connect to a SQL Server
through a WAN.
I'm obviously missing something.
Kyle!
Compare the client netlib configuration between the machines (cliconfg.exe).
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://sqlblog.com/blogs/tibor_karaszi
"Kyle Jedrusiak" <kjedrusiak@.princetoninformation.com> wrote in message
news:ujMzvwWnHHA.5052@.TK2MSFTNGP04.phx.gbl...
> Which talks about Named Pipes.
> We're not using Named Pipes, we're using TCP/IP.
> All of the four other machines work...why not this one.
> Note. It's a machine that has been reformatted and programs reinstalled.
> But my program does nothing special other than connect to a SQL Server through a WAN.
> I'm obviously missing something.
>
> Kyle!
>
|||Since reformatted and reinstalled, how about windows internet firewall is on
(enabled by default when you applied windows xp SP2)? Or another firewall
product perhaps? Can you connect if you explicitly put in the ip address of
the machine in QA/SSMS?
TheSQLGuru
President
Indicium Resources, Inc.
"Kyle Jedrusiak" <kjedrusiak@.princetoninformation.com> wrote in message
news:ujMzvwWnHHA.5052@.TK2MSFTNGP04.phx.gbl...
> Which talks about Named Pipes.
> We're not using Named Pipes, we're using TCP/IP.
> All of the four other machines work...why not this one.
> Note. It's a machine that has been reformatted and programs reinstalled.
> But my program does nothing special other than connect to a SQL Server
> through a WAN.
> I'm obviously missing something.
>
> Kyle!
>