An attempt was made to access a socket in a way forbidden by its access permissions

Question

I have a website on HostGator and a dedicated server of my own running SQL Server 2008R2   The connection string I use is X X X X 1433 which points to the IP address of my dedicated server  I have made the firewall settings on my server so that I can use SSMS  amp  log into SQL Server from my home PC   Having done that  I was under the impression that connecting to SQL from my hostGator hosted-site would work just fine  I receive the following error      A network-related or instance-specific error occurred while establishing a   connection to SQL Server  The server was not found or was not accessible    Verify that the instance name is correct and that SQL Server is configured to   allow remote connections   provider  TCP Provider  error  0 - An attempt was   made to access a socket in a way forbidden by its access permissions     I have looked up this error and found many explanations  but not one dealing with my circumstances  My server is running Windows 2008 w IIS 7 5  I was assured by HostGator tech support that there would be no problems from their end     My firewall allows TCP port 1433   amp  the UDP port 1434 for the SQL Server Browser service   Since I have a dedicated server  I have no one to ask this question to from my hosting company

User · Answer

Just Restart-Service hns can change the port occupier by Hyper-V  It might release the port you need

User · Answer

As per https   stackoverflow com a 33859341 446250  having internet connection sharing enabled for my ethernet adapter ended up causing this problem for me  Disabling the sharing fixed the problem

User · Answer

If You need to access SQL server on hostgator remotely using SSMS  you need to white list your IP in hostgator  Usually it takes 1 hour to open port for the whitelisted IP

User · Answer

My situation and solution  I had created and enabled a HyperV ethernet adapter  For some reason  my main windows machine was using the  virtual  ethernet adapter instead of the  hardware  adapter   I disabled the virtual ethernet and my network settings to change the network public privacy settings were revealed

User · Answer

My windows firewall was blocking port 8080 so i changed it to 5000 and it worked

User · Answer

I had a similar issue with Docker for Windows and Hyper-V having reserved ports for its own use- in my case  it was port 3001 that couldn t be accessed    The port wasn t be used by another process- running netstat -ano   findstr 3001 in an Administrator Powershell prompt showed nothing  However  netsh interface ipv4 show excludedportrange protocol tcp showed that the port was in one of the exclusion ranges    I was able to follow the solution described in Docker for Windows issue  3171  Unable to bind ports  Docker-for-Windows  amp  Hyper-V excluding but not using important port ranges     Disable Hyper-V   dism exe  Online  Disable-Feature Microsoft-Hyper-V  After the required restarts  reserve the port you want so Hyper-V doesn t reserve it back   netsh int ipv4 add excludedportrange protocol tcp startport 3001 numberofports 1  Reenable Hyper-V   dism exe  Online  Enable-Feature Microsoft-Hyper-V  All    After this  I was able to start my docker container

User · Answer

Per this link   the symptom could occur if the replication service tries to use the ports that occupied by others  or by a malfunction NIC  Please try the following steps    Restart the windows firewall service Reboot the problematic machine Restart the    TCP IP stack      Run CMD as administrator  type    netsh int ip reset resetlog txt    to reset TCP IP  Try to temporarily disable antivirus

User · Answer

Not surprisingly  this error can arise when another process is listening on the desired port  This happened today when I started an instance of the Apache Web server  listening on its default port  80   having forgotten that I already had IIS 7 running  and listening on that port  This is well explained in Port 80 is being used by SYSTEM  PID 4   what is that  Better yet  that article points to Stop http sys from listening on port 80 in Windows  which explains a very simple way to resolve it  with just a tad of help from an elevated command prompt and a one-line edit of my hosts file

[sql-server] An attempt was made to access a socket in a way forbidden by its access permissions

Examples related to sql-server

Examples related to sql-server-2008

Examples related to sockets

Examples related to tcp