|
Home > Archive > Microsoft SQL Server Desktop Engine > November 2006 > Issue with Windows Firewall and SQL Server Express 2005
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Issue with Windows Firewall and SQL Server Express 2005
|
|
| danrostron 2006-11-27, 7:18 pm |
| Hi
I have an issue with Windows Firewall and SQL Server on our server.
I have tried to allow remote access to SQL server. The default setup of SQL
server Express is to use dynamic ports. However, beacause we use a firewall,
I need to set one port which all client connections use.
I have done this using SQL Server Configuration Manager, setting the port to
use as 1433. I have then configured the firewall to allow connections to pass
through on this port. This works, however for some unknown reason, it
suddenly stops working (roughly once a day). It reports that 'SQL server
doesn't exist or access denied'. If I restart the firewall, the problem
disappears, but only for another day or so!
After looking at the Application Event Logs, I see the following error, 'The
configuration of the AdminConnection\TCP protocol in the SQL instance
SQLEXPRESS is not valid.'
On searching for this error, I have not found any valid solutions. After
contacting my hosting company, 'Rackspace' they said that they believe the
issue to be a bug in the Windows Firewall.
Is this the case, or are they just trying to get me to rent a hardware
firewall from them at a cost of £70 a month?
Thanks in advance
Dan Rostron.
| |
| Andrea Montanari 2006-11-27, 7:18 pm |
| hi Dan,
danrostron wrote:
> Hi
>
> I have an issue with Windows Firewall and SQL Server on our server.
>
> I have tried to allow remote access to SQL server. The default setup
> of SQL server Express is to use dynamic ports. However, beacause we
> use a firewall, I need to set one port which all client connections
> use.
>
> I have done this using SQL Server Configuration Manager, setting the
> port to use as 1433.
1433 is uually reserved to default SQL Server instances and you should not
use it elsewhere... but, as long as no default SQL Server instance get
installed you should have no additional problem..
>I have then configured the firewall to allow
> connections to pass through on this port. This works, however for
> some unknown reason, it suddenly stops working (roughly once a day).
> It reports that 'SQL server doesn't exist or access denied'.
the "well known" problems related to this exception are listed in
http://support.microsoft.com/defaul...306&Product=sql
.... firewall related problems are included..
>If I
> restart the firewall, the problem disappears, but only for another
> day or so!
>
> After looking at the Application Event Logs, I see the following
> error, 'The configuration of the AdminConnection\TCP protocol in the
> SQL instance SQLEXPRESS is not valid.'
try having a look at
http://blogs.msdn.com/sqlexpress/ar.../23/192044.aspx ...
>
> On searching for this error, I have not found any valid solutions.
> After contacting my hosting company, 'Rackspace' they said that they
> believe the issue to be a bug in the Windows Firewall.
>
> Is this the case, or are they just trying to get me to rent a hardware
> firewall from them at a cost of £70 a month?
I'm not aware of such a problem affecting the windows firewall (but it can
be..) I'm using it on several installations (ok with other ports) but it
does ot seem to be afflicted this way..... just be sure to check the port
you are referencing is not pre-allocated by other services..
--
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz http://italy.mvps.org
DbaMgr2k ver 0.20.0 - DbaMgr ver 0.64.0 and further SQL Tools
--------- remove DMO to reply
|
|
|
|
|