We have SQL 2008 server on our network and I am periodically losing 
connection to SQL Server on my Win 7 PC.  I will be working in and out of 
SSMS all day and then all of a sudden I get "A network-related or 
instance-specific error occurred while establishing a connection to SQL 
Server. The server was not found.........Error: 233"

I then try looking at files on that same server and that works fine so it 
does not appear to be a network issue.  Can anyone help me troubleshoot this?

p.s. If I reboot my workstation then all works fine again.  Thanks.
-- 
David

On Wed, 1 Sep 2010 13:24:06 -0700, DavidC <dlchase@lifetimeinc.com>
wrote:

>We have SQL 2008 server on our network and I am periodically losing 
>connection to SQL Server on my Win 7 PC.  I will be working in and out of 
>SSMS all day and then all of a sudden I get "A network-related or 
>instance-specific error occurred while establishing a connection to SQL 
>Server. The server was not found.........Error: 233"
>
>I then try looking at files on that same server and that works fine so it 
>does not appear to be a network issue.  Can anyone help me troubleshoot this?
>
>p.s. If I reboot my workstation then all works fine again.  Thanks.

You don't say whether this is only the one workstation or not?

The reason could be one of many, from hardware, drivers, software etc.
It used to be a problem with AV software killing named pipe
connections, but you should be using a TCP/IP by default.

If you have a  PC that dioes not display the problem, try swapping the
connections (including the patch cables) to see if it happens. That
would hopefully determine if its the workstation or not.

Jphn

DavidC (dlchase@lifetimeinc.com) writes:
> We have SQL 2008 server on our network and I am periodically losing 
> connection to SQL Server on my Win 7 PC.  I will be working in and out of 
> SSMS all day and then all of a sudden I get "A network-related or 
> instance-specific error occurred while establishing a connection to SQL 
> Server. The server was not found.........Error: 233"
> 
> I then try looking at files on that same server and that works fine so
> it does not appear to be a network issue.  Can anyone help me
> troubleshoot this? 
 
This happens to me at work everyonce in a while. An SQL Server or some
other machine is gone for a while and then it comes back. I've not
dug into it, but it has very little to do with SQL Server, but there is
a general network problem. A short disruption is all it takes.


-- 
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

I will try replacing the network cables and see if that does it.  It just 
seemed strange that I was able to view network files from that server right 
after it happened.  Thanks for your advice.
-- 
David


"John Bell" wrote:

> On Wed, 1 Sep 2010 13:24:06 -0700, DavidC <dlchase@lifetimeinc.com>
> wrote:
> 
> >We have SQL 2008 server on our network and I am periodically losing 
> >connection to SQL Server on my Win 7 PC.  I will be working in and out of 
> >SSMS all day and then all of a sudden I get "A network-related or 
> >instance-specific error occurred while establishing a connection to SQL 
> >Server. The server was not found.........Error: 233"
> >
> >I then try looking at files on that same server and that works fine so it 
> >does not appear to be a network issue.  Can anyone help me troubleshoot this?
> >
> >p.s. If I reboot my workstation then all works fine again.  Thanks.
> 
> You don't say whether this is only the one workstation or not?
> 
> The reason could be one of many, from hardware, drivers, software etc.
> It used to be a problem with AV software killing named pipe
> connections, but you should be using a TCP/IP by default.
> 
> If you have a  PC that dioes not display the problem, try swapping the
> connections (including the patch cables) to see if it happens. That
> would hopefully determine if its the workstation or not.
> 
> Jphn
> .
>