Re: Deploying ASP.NET Application

From: M. Zeeshan Mustafa (zeeshan_at_no-spm.please.zeeshan.net)
Date: 06/29/04 

Date: Tue, 29 Jun 2004 16:55:56 +0500

Hi,

you've said in your early post that your older ASP applications are working
fine in this environment.. I think this is not about firewall port blocking,
its more
likely that you are using integrated security while connecting your
application
to SQL Server?

You should read this blog post:
http://weblogs.asp.net/AChang/archive/2004/04/15/113866.aspx

Good luck 

-- 
Hope this helps,
Zeeshan Mustafa, MCSD
"rlthurston" <rlthurston@discussions.microsoft.com> wrote in message
news:10EDAC27-6BCB-4EB2-A289-EBF3049E0E29@microsoft.com...
> SQL Server does not exist or access denied.
> Description: An unhandled exception occurred during the execution of the
current web request. Please review the stack trace for more information
about the error and where it originated in the code.
>
> Exception Details: System.Data.SqlClient.SqlException: SQL Server does not
exist or access denied.
>
> - the connection string that I am using works for other code that is
deployed on that server - it has something to do with ports on the firewall
that the .net app is trying to communicate on.
>
> "rlthurston" wrote:
>
> > I am in the process of moving our asp.net application from staging
environment to our production environment.  Our security in staging is quite
a bit more lax then in production and when we deployed it - the application
keeps returning errors when trying to connect to SQL Server (2000).  We have
opened the following ports on our firewall to allow communication - 135
(RPC), 80 (HTTP), 1433 (SQL), 1434 (SQL), 21 (FTP).  The really odd thing is
that one our older ASP applications works just fine in this evironment and
connect to the database server with the same exact connection string as the
one we have deployed in the asp.net application.  I am hoping that someone
has run into this problem before and can tell me what other ports are
necessary for asp.net.

Relevant Pages

  • Re: SQL Server 2005 Transaction VPN Firewall
    ... den MSDTC habe ich eingerichtet, wenn ich die Firewall alle Ports aufmache, ... Kann man die Verbindung nicht auf einen festen Port legen? ... wie geht das in SQL Server 2005? ... Ports da genutzt werden. ...
    (microsoft.public.de.sqlserver)
  • Re: SQL Server Specific Windows Firewall Exception
    ... Most corporate environments don't use Microsoft Windows ... Firewall - not because it's too complicated but because it's ... really needed in their environment - they use other ... out what ports to open when and why, ...
    (microsoft.public.sqlserver.connect)
  • Re: Cant replicate between two servers
    ... yes i check to ports in the firewall and it's all opened ... Ping only ... > appropriate permissions to access SQL Server and of course, the ports must ...
    (microsoft.public.sqlserver.replication)
  • Re: Can SQL be told to stop listening on specific IPs on its computer ?
    ... ports on the firewall or in packet filtering on the OS network control ... >> In terms of the IPs and the web addresses, ... >> and SQL Server installed on the same server? ... >>>to tell SQL server what IPs and ports to listen on. ...
    (microsoft.public.sqlserver.security)
  • Re: SQL Server Specific Windows Firewall Exception
    ... their network (and I'm not talking ZoneAlarm, McAfee Personal Firewall, here. ... Microsoft don't have a problem with it considering the exceptions ... Windows Firewall to enable remote access and administration to a SQL Server ... So, if we put aside the whole automatic open ports distraction, wouldn't it ...
    (microsoft.public.sqlserver.connect)