Cannot connect to SQL server over network after SP2

Hello,
I'll try my luck in this group before I re-install the whole thing.
I'm running MS SQL Server 2005 developer edition on the Windows Server
2003 Small Business Edition.
Few days ago I have updated to the SP2 via windows update.
Since then I cannot connect to the SQL server remotely (using
Management Studio).
- If I log remotely to the server box I can connect locally and all
looks fine.
However, from the network it does not work.
- The SQL Server browser is running..
- TCP & Named Pipes are enabled.
- No errors in the Event Viewer
- "Allow remote connections to this server" property is enabled
- Both firewalls (server & client) are off.
- Both authentication types (SQL auth / Windows auth) are not working
Has anyone had similar problem? Any ideas?
Thank you,
Damir SudarevicWhat is the error message you are getting? We just finished installing SP2
on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
log event at all? Or when trying to access the server from remote location
the computer refuses to see the SQL server?
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:
> Hello,
> I'll try my luck in this group before I re-install the whole thing.
> I'm running MS SQL Server 2005 developer edition on the Windows Server
> 2003 Small Business Edition.
> Few days ago I have updated to the SP2 via windows update.
> Since then I cannot connect to the SQL server remotely (using
> Management Studio).
> - If I log remotely to the server box I can connect locally and all
> looks fine.
> However, from the network it does not work.
> - The SQL Server browser is running..
> - TCP & Named Pipes are enabled.
> - No errors in the Event Viewer
> - "Allow remote connections to this server" property is enabled
> - Both firewalls (server & client) are off.
> - Both authentication types (SQL auth / Windows auth) are not working
>
> Has anyone had similar problem? Any ideas?
> Thank you,
> Damir Sudarevic
>|||On Jun 27, 8:12 pm, Mohit K. Gupta
<MohitKGu...@.discussions.microsoft.com> wrote:
> What is the error message you are getting? We just finished installingSP2
> on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
> log event at all? Or when trying to access the server from remote location
> the computer refuses to see the SQL server?
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
> > Hello,
> > I'll try my luck in this group before I re-install the whole thing.
> > I'm running MS SQL Server 2005 developer edition on the Windows Server
> > 2003 Small Business Edition.
> > Few days ago I have updated to theSP2via windows update.
> > Since then Icannotconnectto the SQL server remotely (using
> > Management Studio).
> > - If I log remotely to the server box I canconnectlocally and all
> > looks fine.
> > However, from the network it does not work.
> > - The SQL Server browser is running..
> > - TCP & Named Pipes are enabled.
> > - No errors in the Event Viewer
> > - "Allow remote connections to this server" property is enabled
> > - Both firewalls (server & client) are off.
> > - Both authentication types (SQL auth / Windows auth) are not working
> > Has anyone had similar problem? Any ideas?
> > Thank you,
> > Damir Sudarevic
Hi,
No error messages. The Management Studio (from remote clients - more
than one) simply hangs up.
The studio actually sees the server (in browse servers), but
connection can not be established.
If I log in remotely to the server box and start MS over there it
works fine.
Thanks.|||Hangs up? SO you have to kill the SSMS and then you can use the computer,
only thing I had that is when our network guys mucked up the firewall
settings. Check for port 1433 connection.
--
Mohit K. Gupta
B.Sc. CS, Minor Japanese
MCTS: SQL Server 2005
"Damir" wrote:
> On Jun 27, 8:12 pm, Mohit K. Gupta
> <MohitKGu...@.discussions.microsoft.com> wrote:
> > What is the error message you are getting? We just finished installingSP2
> > on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
> > log event at all? Or when trying to access the server from remote location
> > the computer refuses to see the SQL server?
> >
> > --
> > Mohit K. Gupta
> > B.Sc. CS, Minor Japanese
> > MCTS: SQL Server 2005
> >
> > "Damir" wrote:
> > > Hello,
> >
> > > I'll try my luck in this group before I re-install the whole thing.
> >
> > > I'm running MS SQL Server 2005 developer edition on the Windows Server
> > > 2003 Small Business Edition.
> >
> > > Few days ago I have updated to theSP2via windows update.
> > > Since then Icannotconnectto the SQL server remotely (using
> > > Management Studio).
> >
> > > - If I log remotely to the server box I canconnectlocally and all
> > > looks fine.
> >
> > > However, from the network it does not work.
> >
> > > - The SQL Server browser is running..
> > > - TCP & Named Pipes are enabled.
> > > - No errors in the Event Viewer
> > > - "Allow remote connections to this server" property is enabled
> > > - Both firewalls (server & client) are off.
> > > - Both authentication types (SQL auth / Windows auth) are not working
> >
> > > Has anyone had similar problem? Any ideas?
> >
> > > Thank you,
> >
> > > Damir Sudarevic
> Hi,
> No error messages. The Management Studio (from remote clients - more
> than one) simply hangs up.
> The studio actually sees the server (in browse servers), but
> connection can not be established.
> If I log in remotely to the server box and start MS over there it
> works fine.
> Thanks.
>|||On Jun 29, 1:28 pm, Mohit K. Gupta <mohitkgu...@.msn.com> wrote:
> Hangs up? SO you have to kill the SSMS and then you can use the computer,
> only thing I had that is when our network guys mucked up the firewall
> settings. Check for port 1433 connection.
> --
> Mohit K. Gupta
> B.Sc. CS, Minor Japanese
> MCTS: SQL Server 2005
> "Damir" wrote:
> > On Jun 27, 8:12 pm, Mohit K. Gupta
> > <MohitKGu...@.discussions.microsoft.com> wrote:
> > > What is the error message you are getting? We just finished installingSP2
> > > on SQL 2005 EE, and no problems at all. Does it contain Login Failed error
> > > log event at all? Or when trying to access the server from remote location
> > > the computer refuses to see the SQL server?
> > > --
> > > Mohit K. Gupta
> > > B.Sc. CS, Minor Japanese
> > > MCTS: SQL Server 2005
> > > "Damir" wrote:
> > > > Hello,
> > > > I'll try my luck in this group before I re-install the whole thing.
> > > > I'm running MS SQL Server 2005 developer edition on the Windows Server
> > > > 2003 Small Business Edition.
> > > > Few days ago I have updated to theSP2via windows update.
> > > > Since then Icannotconnectto the SQL server remotely (using
> > > > Management Studio).
> > > > - If I log remotely to the server box I canconnectlocally and all
> > > > looks fine.
> > > > However, from the network it does not work.
> > > > - The SQL Server browser is running..
> > > > - TCP & Named Pipes are enabled.
> > > > - No errors in the Event Viewer
> > > > - "Allow remote connections to this server" property is enabled
> > > > - Both firewalls (server & client) are off.
> > > > - Both authentication types (SQL auth / Windows auth) are not working
> > > > Has anyone had similar problem? Any ideas?
> > > > Thank you,
> > > > Damir Sudarevic
> > Hi,
> > No error messages. The Management Studio (from remote clients - more
> > than one) simply hangs up.
> > The studio actually sees the server (in browse servers), but
> > connection can not be established.
> > If I log in remotely to the server box and start MS over there it
> > works fine.
> > Thanks.
Works!
Thank you Mohit, it was (something) about the ports. Changed TCP ports
to Dynamic and everything started working. Not quite sure what is
dynamic vs 1433; but as long as it works...
Thanks again,
Damir