I can't connect to an SQL2008 server on a WS2008 server. I have set the server connections property to allow remote connections. I have enabled the firewall port 1433 for TCP. I have enabled the firewall port 1434 for UDP. This is a named instance on a server without a default instance. I can turn off the firewall and connections will work. Is the 'Name:' field in the 'Edit a Port' firewall dialog significant or is it just for documentation? Does it need to include the instance name? What else am I missing? Thanks Tom
Hello Tom, A SQL Server Named Instance does not use a static port by default, instead it uses a dynamic port and it'll not be "1433" probably. You may want to configure your SQL Server Instance to use a static port instead and you'd use this port number while making a connexion to your SQL Server Instance? You also may want to insert another exception a program name (Add Program in Windows Firewall settings, in the Exceptions tab) for your SQL Server Instance' s application file. You may want to see this link too: Configuring the Windows Firewall to Allow SQL Server Access http://msdn.microsoft.com/en-us/library/cc646023.aspx -- Ekrem Ãnsoy "Tom" wrote in message news:9AFF1304-ED2E-4CE1-8637-1E9AF9CDC9FB@microsoft.com... >I can't connect to an SQL2008 server on a WS2008 server. > I have set the server connections property to allow remote connections. > I have enabled the firewall port 1433 for TCP. > I have enabled the firewall port 1434 for UDP. > > This is a named instance on a server without a default instance. > I can turn off the firewall and connections will work. > > Is the 'Name:' field in the 'Edit a Port' firewall dialog significant or > is > it just for documentation? Does it need to include the instance name? > > What else am I missing? > > Thanks > Tom
Adding the program exception seems to have solved the problem. Thanks Tom "Ekrem Ãnsoy" wrote: > Hello Tom, > > A SQL Server Named Instance does not use a static port by default, instead > it uses a dynamic port and it'll not be "1433" probably. > > You may want to configure your SQL Server Instance to use a static port > instead and you'd use this port number while making a connexion to your SQL > Server Instance? > > You also may want to insert another exception a program name (Add Program in > Windows Firewall settings, in the Exceptions tab) for your SQL Server > Instance' s application file. > > You may want to see this link too: > Configuring the Windows Firewall to Allow SQL Server Access > http://msdn.microsoft.com/en-us/library/cc646023.aspx > > -- > Ekrem Ãnsoy > > > > "Tom" wrote in message > news:9AFF1304-ED2E-4CE1-8637-1E9AF9CDC9FB@microsoft.com... > >I can't connect to an SQL2008 server on a WS2008 server. > > I have set the server connections property to allow remote connections. > > I have enabled the firewall port 1433 for TCP. > > I have enabled the firewall port 1434 for UDP. > > > > This is a named instance on a server without a default instance. > > I can turn off the firewall and connections will work. > > > > Is the 'Name:' field in the 'Edit a Port' firewall dialog significant or > > is > > it just for documentation? Does it need to include the instance name? > > > > What else am I missing? > > > > Thanks > > Tom >
