gacto
asked on
Windows Server 2012 R2 Firewall
I have two servers set up for a dev environment, one will run code and the other will be dedicated DB. I have both servers running but I cannot get the dev server connected to the DB server over port 1433. I have set an allow rule on the db server for the connection over 1433, binding it to the public IP address of the dev server, but when I attempt a telnet from the dev server to the db server the connection fails.
There are no firewalls in play here other than Windows Firewall. I am not extremely with windows firewall configurations so I feel like I am overlooking a step somewhere.
I need help establishing the rule needed to allow communication between the two servers, through the windows firewall, over port 1433.
There are no firewalls in play here other than Windows Firewall. I am not extremely with windows firewall configurations so I feel like I am overlooking a step somewhere.
I need help establishing the rule needed to allow communication between the two servers, through the windows firewall, over port 1433.
Bryant Schaper
open 1434 as well
ASKER
i have added 1434 to the inbound rule on the db server and still cannot telnet in from the dev server.
you mean telnet just to confirm the port it open or actually telnet to the server?
ASKER
yes i am using telnet just to confirm the port is open. my actual connection will be through code in our API layer.
So you have inbound TCP 1433-1434 open and still no luck?
Let's rule out which end, disable the firewall and test, also try management studio.
Let's rule out which end, disable the firewall and test, also try management studio.
ASKER
ok your comment made me think of something i had not done. i had not configured tcp/ip for sql so i have updated that thru configuration manager and gotten tcp/ip enabled.
i turned off the firewall on the db server and tried to telnet over port 1433, but still no luck.
next i turned off the firewall on the dev server (at this point the firewall on both servers are off) and tried to telnet over port 1433, still no luck.
i am able to connect FROM the db server TO the dev server over port 80 without any problem. so there is definitely connectivity between the servers.
i turned off the firewall on the db server and tried to telnet over port 1433, but still no luck.
next i turned off the firewall on the dev server (at this point the firewall on both servers are off) and tried to telnet over port 1433, still no luck.
i am able to connect FROM the db server TO the dev server over port 80 without any problem. so there is definitely connectivity between the servers.
is their a firewall between, and we are connecting with IP, not named pipes?
ASKER
there is no firewall in between, actually let me clarify. these are GoDaddy VPS machines that i have just set up. i have not set up a firewall on the devices because they r only for dev so we will be tearing them down and rebuilding quite frequently. based on the information i have been provided by GoDaddy, and from the documentation they have on their site, they do not have firewalls in place by default that restricts traffic to or from the machines. so i guess my answer should be that to the best of my knowledge there is no firewall.
i am using IP for the connection, not named pipes. both of the servers have both a public and private IP. i have tried both and the results are the same.
i am using IP for the connection, not named pipes. both of the servers have both a public and private IP. i have tried both and the results are the same.
it looks like they might have a crude form of one like Azure. Can you check
https://www.godaddy.com/he
https://www.godaddy.com/he
ASKER
I am checking this now but so far I cannot access the simple control panel from either the dev or db server. If I can access this control panel, hopefully I will be able to resolve the problem.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
this had to be an internal firewall issue with GoDaddy.