Windows couldn’t automatically bind the IP protocol stack to the network adapter.

Welcome to Microsoft Answers Forum !

To assist you better I would like to ask you a question.

a) Have you made any recent changes on your computer?

Step 1:

I would suggest you to run network diagnostic tool.

To perform this troubleshooting problem, please follow the steps below.

a) Click on Start > Control Panel.

b) Click on Network and Internet, and then click on Network and Sharing center.

c) Under Network and Sharing centre, click on Troubleshoot Problem.

Step 2:

If this doesn’t helps. Then install the latest drivers for the network adaptor from the manufacturer’s website.

If this doesn’t fix the issue, then go ahead with the step 3.

Step 3:

Also I would suggest you to reset the network adaptor settings. Then follow the steps below

To reset the TCP/IP stack go to this article and either click on «Fix it for me» or follow the instructions to fix it yourself:

Disable the IP Helper service:
1. Hold the Windows key and type R, enter «services.msc» (without the quotes) and press Enter
2. Scroll down to the IP Helper service, right click on it and select Properties
3. In the dropdown box that says «Automatic» or «Manual», set it to Disabled and then click on «Apply»
4. Then click on «Stop» to stop the service from running in the current session
5. Click OK to exit the dialog

Disable IPv6:
Try uninstalling IPv6 on all interfaces, removing any IPv6 virtual adapters, and resetting the TCP/IP stack. To remove IPv6, go into the properties for each network adapter and either uncheck the box next to the protocol «Internet Protocol version 6 (TCP/IPv6), that will disable it, or select it and click uninstall, which will remove it off the computer. Then go into device manager and remove any 4to6 adapters, WUN miniport adapters, or tunnel adapters.

NOTE: You should do this for each network connection.

Important: This section, method, or task contains steps that tell you how to modify the registry. However, serious problems might occur if you modify the registry incorrectly. Therefore, make sure that you follow these steps carefully. For added protection, back up the registry before you modify it. Then, you can restore the registry if a problem occurs. For more information about how to back up and restore the registry, click the following article number to view the article in the Microsoft Knowledge Base:
http://support.microsoft.com/kb/322756

(How to back up and restore the registry in Windows)
Windows Vista cannot obtain an IP address from certain routers or from certain non-Microsoft DHCP servers
To resolve this issue, disable the DHCP BROADCAST flag in Windows Vista. To do this, follow these steps:

1. Click Start, type regedit in the Start Search box, and then click regedit in the Programs list.
If you are prompted for an administrator password or for confirmation, type your password, or click Continue.
2. Locate and then click the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Tcpip\Parameters\Interfaces\
3. In this registry path, click the (GUID) subkey that corresponds to the network adapter that is connected to the network.
4. On the Edit menu, point to New, and then click DWORD (32-bit) Value.
5. In the New Value #1 box, type DhcpConnEnableBcastFlagToggle, and then press ENTER.
6. Right-click DhcpConnEnableBcastFlagToggle, and then click Modify.
7. In the Value data box, type 1, and then click OK.
8. Close Registry Editor.

By setting this registry key to 1, Windows Vista will first try to obtain an IP address by using the BROADCAST flag in DHCP Discover packets. If that fails, it will try to obtain an IP address without using the BROADCAST flag in DHCP Discover packets .

I hope that this information helps. Please get back to us if you have any more questions about this issue.

Thanks and Regards
Mir — Microsoft Answers Support Engineer
Visit our Microsoft Answers Feedback Forum and let us know what you think

Cannot bind to some ports due to permission denied

For the last 3 months or so I’m having random errors where I can’t bind a specific port where our Identity server is running on my local development workstation. At first I thought it’s my broken machine, so I reset everything, which kinda fixed the issue for 2 months and now it is back.

In the meanwhile other developers saw the same issue. All of us who experience the issue are running Windows 10, but not everyone with Windows 10 has that issue.

Restarting windows after it was shut down with shutdown /s /f /t 0 is the only reliable solution to open up the port again. After I restart normally (due to windows updates or similar) the issue comes up again an I need to shut down windows with that command.

I wrote a small f# script to test which ports are affected. The exact error message I get is

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

When I looked for it, the suggested solutions where to restart the machine, but that seems more like a work around, not a real solution. I’ve also found https://stackoverflow.com/a/10461978/621366 — but netstat -o doesn’t list the port, neither does the tool TCPView. All of us are pretty sure that the port isn’t occupied by anything. I also tried running netstat in an administrator console and similar commands inside bash on windows, but couldn’t find anything. I can’t even connect to the port via telnet, it says nothing is listening on the port.

those ports in question are for instance:

• 49670 — 49689
• 49710 — 49749
• 49760 — 49779
• 49811 — 49830
• 49843 — 49882
• 50197 — 50216

None of us modified anything on the windows firewall or has any additional anti virus tools installed except the windows 10 default ones. So everything should be on default values. And it also worked normally for

10 months before it broke the first time and afterwards for 2 months. In both cases after some windows updates where installed. The last time it was a bios update (probably due to the meltdown / spectre issues?).

Also trying to open up the ports explicitly on the firewall didn’t help.

According to this answer https://stackoverflow.com/a/23982901/621366 TCPView and netstat shouldn’t miss any occupied ports, but even when I enable showing unconnected endpoints in TCPView, I don’t see any of the ports where I get permission denied when trying to bind them. Here a screen from the occupied ports (I marked the bordering occupied ports which are right before or after the group of permission-denied-ports)

UPDATE:

I’ve noticed that it always seems to be 160 or 180 (exact numbers) of ports which have permission denied in the ranges of 40,000+ This seems oddly coincidental to me, so obviously something is occupying the ports on purpose, but what? I can’t seem to find anything in the windows event logs (although I wouldn’t know what to look for exactly) and none of those ports shows up any any of my firewall rules. Also shutting down docker for windows doesn’t make any difference and when a colleague mentioned that for them it’s enough to restart docker for windows (in the UI go to Reset->Restart) and right now for me, even restarting with the shutdown command doesn’t work anymore.

UPDATE 2:

The output of netstat -ano run from an administrator powershell:

The f# code I used to test for open ports:

and the output when executing the application (it was executed right after the netstat command):

The port which I’d actually want to have opened is 49786 but the amount of ports reported with permission denied by my small testing algorithm, but not allocated when checking netstat is confusing me

UPDATE 3:

Now that simply running shutdown /s /f /t 0 doesn’t work anymore, I’ve found another workaround which seems to be working fairly reliably in https://social.technet.microsoft.com/Forums/windows/en-US/e0cc1b3e-2c63-451a-abc8-8e1e66a23287/an-attempt-was-made-to-access-a-socket-in-a-way-forbidden-by-its-access-permissions?forum=w7itpronetworking — netsh int ip reset and restarting the computer (normal windows 10 restart is enough) and the port was consistently available on the next start so far (but it was just 3 tries)

UPDATE 4:

Summary of the comments:

• setting SO_REUSEADDR in the small f# script makes things only worse
• trying to close skype, VPN applications, dropbox and similar didn’t have any effect (yes I actually made sure that the processes are terminated)

Can’t bind TCP listener *:6379 using Redis on Windows

I’m using Redis 2.8 on Windows which I downloaded from github release. After unzip and I’ve set maxheap in redis.windows.conf file. After running redis-server redis.windows.conf I get # Creating Server TCP listening socket *:6379:No such file or directory , but redis is not running correctly. I don’t know why.

9 Answers 9

You must’ve used the .msi installer. It automagically registers a windows service which starts instantly after the installation (at least on my win 10 machine).

This service uses the default config and binds to port 6379. When you start redis-server from the command line, if you haven’t specified a different port through a config file, it picks up the default config again and tries to bind to port 6379 which fails.

Your cli works because it connects to the redis service that’s already listening on 6379. Your shutdown command stops the service and from there things work as expected. Mystery solved. Case closed.

cd to the bin directory of Redis, and run

open another cmd window, cd to the bin directory of Redis, and run

Now service is normally.I run redis-cli.exe in the same window,and it connect correctly.Then I typed shutdown,the service is over.Reopen a command windows,type redis-server .The service run correctly.But I still did not understand why # Creating Server TCP listening socket *:6379:No such file or directory came out.

We had a similar/related «redis-server.exe» service hosting issue.

After installing the Redis Windows Service, we could access the service on port 6379 locally, but not from a remote client (even though the firewall was configured to allow inbound traffic on the port).

In order to resolve the issue, we had to edit the redis.windows-service.conf configuration file and change the following:

• bind 127.0.0.1 needed use the actual IP address
• protected-mode yes needed to be set to «no»

After making the above changes, we restarted the Redis service and were able to connect from all clients.

After getting this error,open the cli and press the command ‘shutdown’ and restart redis server. You are good to go. You will get the logo and everything is as expected.

1. check the port(if something else is using redis port)
2. use redis-server xxx.conf to run a server with your configuration
3. try to use redis-cli

C:\redis>redis-server.exe —service-install [8124] 03 Feb 23:58:14.573 # HandleServiceCommands: system error caught. error c ode=1073, message = CreateService failed: unknown error

C:\redis>redis-server —service-install redis.windows.conf —loglevel verbose [10848] 04 Feb 00:00:40.508 # HandleServiceCommands: system error caught. error code=1073, message = CreateService failed: unknown error

C:\redis>redis-server —service-install -–service-name redisService1 –port 100 01 Failed to open the .conf file: 10001 CWD=C:\redis

Question: Q: Cannot bind to windows domain

Mac book and imac, Mac OS X (10.6.3)

Posted on Apr 12, 2010 3:31 AM

All replies

Loading page content

Page content loaded

I have the same. It works with admitmac, but I don’t want to use additional software. Anybody a hint? I tried everything I could imagine or find on the internet.

Apr 20, 2010 12:13 PM

May 4, 2010 5:17 AM

May 4, 2010 5:26 AM

Maybe the tutorial in the blog How to Set Up a Mac on a Windows Domain might help everybody’s Domain problem.

Plus anyone putting a lone Mac into Windows Domains should bookmark the MacWindows.com. Their reader reports on the right side (of the main page) are a resource for great tips.

Message was edited by: satcomer

May 6, 2010 2:53 PM

I’ve tried just about everything I could think of or google for:
— disable smb signing
— allow unsigned LDAP communication
— modify dsHeuristics on the AD server
— disable offload of network card
— added local domain to the mac DNS search (just in case, should not be needed on 10.6)
— make sure that DNS is working well
— ping works, smb works, exchange works, all works,
— .
— except binding to the domain.

I’m sure I’m using the correct domain account.
Logging does not help much. One strange error message I get:

19/06/10 19:00:15 System Preferences[121] -[ODCAddServerSheetController handleOtherActionError: gotError: Error Domain=com.apple.OpenDirectory Code=4001 UserInfo=0x200476920 «Custom call 85 to Active Directory failed.», Operation was denied because the current credentials do not have the appropriate privileges.

So it looks like something on the SBS 2008 machine. But all is ok there, as far as I can see!

Also an extract of DirectoryServices.debug.log (replaced actual domain name with xxxxxx). Seems to fail after step 4, step 5 is never started.

DirectoryService.debug.log.8:2010-06-19 12:19:52 CEST — T[0x0000000101A81000] — Active Directory: Bind Step 1 — Searching for Forest/Domain information
DirectoryService.debug.log.8:2010-06-19 12:19:52 CEST — T[0x0000000101A81000] — Active Directory: xxxxxx.local — Start checking servers for site «any»
DirectoryService.debug.log.8:2010-06-19 12:19:52 CEST — T[0x0000000101A81000] — Active Directory: Total Servers «any» LDAP — 1, Kerberos — 1, kPasswd — 1
DirectoryService.debug.log.8:2010-06-19 12:19:52 CEST — T[0x0000000101A81000] — Active Directory: DomainConfiguration reachabilityNotification — Node: xxxxxx.local — resolves — enabled
DirectoryService.debug.log.8:2010-06-19 12:19:52 CEST — T[0x0000000101A81000] — Active Directory: Bind Step 2 — Finding nearest Domain controllers
DirectoryService.debug.log.8:2010-06-19 12:19:52 CEST — T[0x0000000101A81000] — Active Directory: Bind Step 3 — Verifying credentials
DirectoryService.debug.log.8:2010-06-19 12:19:52 CEST — T[0x0000000101A81000] — Active Directory: lockLDAPSession — unable to establish a connection to xxxxxx.local
DirectoryService.debug.log.8:2010-06-19 12:19:53 CEST — T[0x0000000101A81000] — Active Directory: Password verify for it@XXXXXX.LOCAL succeeded — cache MEMORY:tkZ2qa9
DirectoryService.debug.log.8:2010-06-19 12:19:53 CEST — T[0x0000000101A81000] — Active Directory: Bind Step 4 — Searching for existing computer
DirectoryService.debug.log.8:2010-06-19 12:19:53 CEST — T[0x0000000101A81000] — Active Directory: lockLDAPSession — unable to establish a connection to xxxxxx.local
DirectoryService.debug.log.8:2010-06-19 12:19:53 CEST — T[0x0000000101A81000] — Active Directory: Password verify for it@XXXXXX.LOCAL succeeded — cache MEMORY:5BSBZMr

If anybody still has an idea how to fix, I’d greatly appreciate.