lianne143
asked on
Do i need to add SQLBrowser & SQLServer on the outbound policy on the SQL server firewall . If Connection failed for login(user), reason:0 ,
Hi
I have migrated the old SQL database from old server to our new SQL 2012 which is installed on windows 2012 Server. I was told to add SQLBrowser & SQLServer Services to the list of exceptions on the SQL server Firewall.
So executed the following from the CMD prompt.
echo Enabling SQL Server Browser Service port 2382
netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=TCP localport=2382
@echo Enabling SQLServer default instance port 1433
netsh advfirewall firewall add rule name="SQL Server" dir=in action=allow protocol=TCP localport=1433
Now when I connect to the SQL server from the win 7 client PC I get error "connection failed for login reason:0"
I tried disabling the firewall on the SQL server and tried again from the win7 PC and it successfully connect to the database server, so it looks like I have to make changes on the SQL server firewall.
So do I need to configure a outbound policy on the SQL firewall for SQLBrowser & SQLServer and If so see below the syntax.Is this a right command that I need to execute on the CMD prompt on the SQL server.
echo Enabling SQL Server Browser Service port 2382
netsh advfirewall firewall add rule name="SQL Browser" dir=out action=allow protocol=TCP localport=2382
@echo Enabling SQLServer default instance port 1433
netsh advfirewall firewall add rule name="SQL Server" dir=out action=allow protocol=TCP localport=1433
Please suggest any help much appreciated.
Thanks in advance.
I have migrated the old SQL database from old server to our new SQL 2012 which is installed on windows 2012 Server. I was told to add SQLBrowser & SQLServer Services to the list of exceptions on the SQL server Firewall.
So executed the following from the CMD prompt.
echo Enabling SQL Server Browser Service port 2382
netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=TCP localport=2382
@echo Enabling SQLServer default instance port 1433
netsh advfirewall firewall add rule name="SQL Server" dir=in action=allow protocol=TCP localport=1433
Now when I connect to the SQL server from the win 7 client PC I get error "connection failed for login reason:0"
I tried disabling the firewall on the SQL server and tried again from the win7 PC and it successfully connect to the database server, so it looks like I have to make changes on the SQL server firewall.
So do I need to configure a outbound policy on the SQL firewall for SQLBrowser & SQLServer and If so see below the syntax.Is this a right command that I need to execute on the CMD prompt on the SQL server.
echo Enabling SQL Server Browser Service port 2382
netsh advfirewall firewall add rule name="SQL Browser" dir=out action=allow protocol=TCP localport=2382
@echo Enabling SQLServer default instance port 1433
netsh advfirewall firewall add rule name="SQL Server" dir=out action=allow protocol=TCP localport=1433
Please suggest any help much appreciated.
Thanks in advance.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
Previously I opened port 2382 for SQL Server Browser through the following command , so do I need to remove the port that I opened previously and change the port to 1433 for SQL Server Browser
echo Enabling SQL Server Browser Service port 2382
netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=TCP localport=2382
Thanks
echo Enabling SQL Server Browser Service port 2382
netsh advfirewall firewall add rule name="SQL Browser" dir=in action=allow protocol=TCP localport=2382
Thanks
ASKER
Sorry , I was not wearing my goggles, I will open inbound UDP port 1434 for SQL Server Browser on the server and post you the results.
thanks
thanks
ASKER
Hi Mahesh
I don't know how much thanks to say to you.
Thanks you so much and now the client connects successfully to our new DB server :)
As you said I opened inbound UDP port 1434 for SQL browser and TCP port 1433 for SQL Server
I don't know how much thanks to say to you.
Thanks you so much and now the client connects successfully to our new DB server :)
As you said I opened inbound UDP port 1434 for SQL browser and TCP port 1433 for SQL Server
ASKER