Re: SQL 2005 Remote Connection Error

I expressed that badly. The error log records the port number at the time of startup. So I see an entry in the SQL Server error log:
Server is listening on [ 'any' <ipv4> 1433].
Search your error log for "Server is listening on" and see if it's there. If not, restart SQL Server. But you just did that, so you should find something. But it might not be port 1433.
--
Rick Byham (MSFT)
This posting is provided "AS IS" with no warranties, and confers no rights.

"AccessARS" <AccessARS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message news:4191CAAF-B3D5-4B9A-9293-4A1DC1723331@xxxxxxxxxxxxxxxx
I found the logs in Management Studio Management>>SQL Server Logs>>Current..
on the server but can't seem to find any information about the port or Errors
that correspond with the date/time of my connection attempts...

"AccessARS" wrote:

I have restarted the SQL Server Integration Services and even the SQL Server
if that's what you are asking. I don't seem to have permission to view the
error log folder (C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Log\)
on my remote desktop, where I am attempting to connect to the SQL Server.
Not sure where to look for that...? Can I check it directly on the
server...and where?

Thank you in advanced for you assistance.

"Rick Byham, (MSFT)" wrote:

> Has the SQL Server service been stopped and restarted since you enabled
> TCP/IP or named pipes?
> Use the remote desktop and check the SQL Server error log. About 1 > screen
> down from the top it will say what TCP/IP port it is listening on. Is > it
> 1433?
> -- > Rick Byham (MSFT)
> This posting is provided "AS IS" with no warranties, and confers no > rights.
>
> "AccessARS" <AccessARS@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> news:23DA6A0F-B4D3-45E7-A5F7-435D3A4C7548@xxxxxxxxxxxxxxxx
> > Currently we have a SQL Server 2005 Standard edition installed on a
> > Microsoft
> > Windows Server 2003 Enterprise Edition SP2. When I try to log in > > through
> > my
> > SQL Management Studio from my desktop with my Windows Authentication > > on
> > our
> > LAN it gives me the following error...
> >
> > "An error has occurred while establishing a connection to the server.
> > When
> > connecting to SQL Server 2005, this failure may be caused by the fact > > that
> > under the default settings SQL Server does not allow remote > > connections.
> > (provider: Named Pipes Provider, error: 40 - Could not open a > > connection
> > to
> > SQL Server) (Microsoft SQL Server, Error: 1326)"
> >
> > ...I am able to login to the server through remote dektop and log in > > to
> > the
> > database through management studio on the server with my windows
> > authentication. Therefore I have checked Start>Programs>Microsoft > > SQL
> > Server
> > 2005>Configuration Tools>SQL Surface Area Configuration>> Surface > > Area
> > Configuration for Services And Connections for the Remote Connections
> > setting
> > in the Database Engine section and it's already set on the Local and
> > remote
> > connections radio button using both TCP/ip and named pipes.
> >
> > On the other hand under SQL Server Browser>>Service>>
> > Startup type: Disabled
> > Service status: Stopped
> >
> > ...does this have anything to do with my issue?
> >
> > Also, I tried setting up a role for myself on the database engine > > level as
> > an admin/owner but the same error persists from my remote desktop.
> >
> > FYI: I have tried registering the server with named pipes and IP > > from the
> > remote client with the same result.
> >
> > Please help!
> >
>

.