• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 60
  • Last Modified:

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.
0
gacto
Asked:
gacto
  • 7
  • 5
1 Solution
 
Bryant SchaperCommented:
open 1434 as well
0
 
gactoAuthor Commented:
i have added 1434 to the inbound rule on the db server and still cannot telnet in from the dev server.
0
 
Bryant SchaperCommented:
you mean telnet just to confirm the port it open or actually telnet to the server?
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
gactoAuthor Commented:
yes i am using telnet just to confirm the port is open. my actual connection will be through code in our API layer.
0
 
Bryant SchaperCommented:
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.
0
 
gactoAuthor Commented:
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.
0
 
Bryant SchaperCommented:
is their a firewall between, and we are connecting with IP, not named pipes?
0
 
gactoAuthor Commented:
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.
0
 
Bryant SchaperCommented:
0
 
gactoAuthor Commented:
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.
0
 
gactoAuthor Commented:
Bryant - Ok it has taken me several days but I have finally resolved the issue. Unfortunately I cannot tell you what actually worked.

I finally had to get on a support session with GoDaddy, they were adamant there is no other firewall in place which could be blocking this connection. However, after about an hour of troubleshooting, the connection starts working. They cannot offer any explanation why. I believe there had to be a bug in the network connection there that one of the technicians resolved, maybe even unknowingly. In any event the connection is running now.

Thanks for the effort and troubleshooting tips. Hopefully the connection will stay up and I won't have this problem anymore.
0
 
gactoAuthor Commented:
this had to be an internal firewall issue with GoDaddy.
0

Featured Post

Has Powershell sent you back into the Stone Age?

If managing Active Directory using Windows Powershell® is making you feel like you stepped back in time, you are not alone.  For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why.

  • 7
  • 5
Tackle projects and never again get stuck behind a technical roadblock.
Join Now