Hi James,
I don't know the answer on your question but I was taught to always change the default SQL Server port and use something else instead.
>All,
>
>We have just upgraded one of our networks from a Windows NT 4.0 Domain to a Windows 2003 Server AD Domain. SQL Server 2000 was installed on one of the DCs and the database was restored to the Server. The problem is that I can not set up a DSN on any of the Clients without explicitly naming the port. We have the SQL Server set to the Default Port 1433. If I go to a client PC runing XP Pro and set up a DSN using the Default Settings, I cannot get a connection to the Database. If I go into the Client configuration of the ODBC Manager and uncheck the "Dynamically Determine Port" checkbox, then manually type in port 1433, I get a connection. Can anyone assist me in figuring out why the Dynamic Port detection is not working and what I can do to resolve the problem?
>
>
>PS; The Windows 2003 Server that SQL is running on is a DC and the Windows 2003 Server Version is 5.2.3790 SP2.
>
>Thanks,
>
>Jim Harvey
If it's not broken, fix it until it is.
My Blog