Windows 2003 - SQL Server does not exist or access denied

[ssp]

G'Day All,

I have a web application sitting on my laptop and a Sql Server 2000
database on our INTRANET server running Windows 2003. Up until recently
I was able to access the database using my application. But recently it
started to give me the error as below:
*************** *
SQL Server does not exist or access denied.

Exception Details: System.Data.Sql Client.SqlExcep tion: SQL Server does
not exist or access denied.

[SqlException: SQL Server does not exist or access denied.]
System.Data.Sql Client.Connecti onPool.GetConne ction(Boolean&
isInTransaction ) +484

System.Data.Sql Client.SqlConne ctionPoolManage r.GetPooledConn ection(SqlConne ctionString
options, Boolean& isInTransaction ) +372
System.Data.Sql Client.SqlConne ction.Open() +384
RingtonesCompon ents.Data.ViewC at1() in C:\dev\xxx\Data .cs:371
RingtonesCMS.Gr ab.AddCat1.Page _Load(Object sender, EventArgs e) in
C:\dev\xxx\cms\ Grab\AddCat1.as cx.cs:33
System.Web.UI.C ontrol.OnLoad(E ventArgs e) +67
System.Web.UI.C ontrol.LoadRecu rsive() +35
System.Web.UI.C ontrol.LoadRecu rsive() +98
System.Web.UI.C ontrol.LoadRecu rsive() +98
System.Web.UI.P age.ProcessRequ estMain() +750

*************** *

I have the following connection string in web.config file:

*************** *
<add key="sqlConnect ion1.Connection String" value="workstat ion
id=SUVPR;packet size=4096;user id=sa;data source=INTRANET ;persist
security info=True;initi al catalog=rington es;password=xxx " />
*************** *

I am completely baffled by the situation.

I can access the INTRANET database using the Enterprise Manager on my
machine.

Any clues will be greatly appreciated.

SSP

[ssp]

Found the solution... A very odd one though. Someone from Microsoft
should better explain this. Infact the problem and the solution is not
an ASP.NET one at all.

Well, what I did was change the TCP/IP Port from 1433 to 1096.
Restarted the Sql Server and ran my application. Still had the "Access
Denied" error. So I decided to revert to Port 1433 and restart the Sql
Server. I ran the application and it worked like a charm.

A complete fluke!

SSP.