Can't bind IP protocol stack to network adapter

Hi Ron,

Did you get this fixed?  If not, I know that the Fixit tool from Microsoft is supposed to reset the tcp/ip stack but maybe trying to reset tcp/ip manually might help? Or did you try that already?

I'm wondering if you're able to ping the router during that few minutes that it isn't "connecting"?

EDIT:  Another thought.  Although you're not able to get to the internet during those 5 minutes, is your router assigning you a standard 192.168 IP address?

Todd

Todd-

Thanks for response. I tried the Fix-It tool but no help. Manually reset tcp/ip etc, no help there either.

Don't have a router. I have FiOS service and my house has an Ethernet jack in every room that goes straight to the ISP's server.

If I click the Network icon on taskbar during those first 5 min, it says "No connections available". And when I run the Network troubleshooter I got that error about not binding IP protocol stack in those first 5 min. And then suddenly it comes up saying "Currently connected to: Network" and everything is fine until the next boot.

I see lots of posts around the net with a similar problem and I've tried virtually every fix suggested. Some have suggested that the only real fix is to reinstall Win 7...  :emotion-41:

All other suggestions gratefully accepted and tried...

Ron,

Start, all programs, accessories, right click on command prompt, left click run as administrator. Type

netsh winsock reset catalog

This will reset the winsock catalog

I saw most of the command without the words catalog so I wonder if the new command works.

Rick

Thanks Rick...no cigar... Still have same issue.

Thought I found the problem last night. Noticed the BITS service was never starting even though it was set to Automatic(Delayed Start).  Set it to Automatic and rebooted, BITS started, but still the delayed network connection.

Starting to wonder if this is an ISP issue. The NIC is set to obtain an IP address automatically from the ISP. Wonder if the ISP's server isn't providing the address promptly so I get "No connections available" on the taskbar and the binding error when I run the network troubleshooter.

Send email to the ISP asking if they could let me test a static IP address...

Don't have a router. I have FiOS service and my house has an Ethernet jack in every room that goes straight to the ISP's server.

Hi,

I've never played witht the FiOS service much but ....   does that mean that your system is provided an IP address directly by the ISP servers?   Do you get full IP addresses or do you still end up getting a 192.168 address?  The reason I ask is your system needs an IP address to be able to communicate with the internet (and the servers from your ISP).  Normally a handshake protocol is sent out to the router (in this case your ISP servers) requesting an IP address.   Normal home routers, using DHCP, assign your system an address within the 192.168.0.1 range.   I'm assuming in your setup the ISP servers do the same process.

If a windows based system does not receive a DHCP assigned IP address then Windows auto assigns it a 169.254.0.1 address range address.  

So if we can find out which IP address your system has during that five minutes we can get an idea of whether the ISP servers are responding normally, but it's a different issue, or if your system isn't getting responses fast enough so it's assigning a default number, etc.

Follow Rick's instructions from above on how to open a command window but please type in:

ipconfig /all

You should see a screen that looks like this afterward:

What we need to know is under the Ethernet adapter section, the IPv4 address that is listed.  In this example it's 192.168.1.103.

I'd be interested to know what IP address the ISP assigns to you afterward as well.   My thinking is, if it's a slow DHCP address assignment from the ISP, would it be possible to statically assign your system an address so it doesn't have to wait 5 minutes to connect through.   

I know it's possible to do so, and I would do it with a home system / router.  But ISPs don't like you statically assigning their IP addresses because they assign them out to customers as they log in, randomly or in a set order.  

Sorry for the long, rambling, post.   I sort of typed it as my brain was thinking it, so if something isn't clear please let me know.   

:)

Todd

Thanks Todd!

Here's IPconfig /all before and after the connection is established. It's not seeing the Broadcom NIC at all so it's not auto-assigning a default IP address. When the connection is established, it shows everything correctly.

BEFORE:

AFTER CONNECTION ESTABLISHED

Ron,

Looked at my notes, The command that I have for the IP Stack reset is

netsh int ip reset resetlog.txt

Strange that the DHCP is not enabled. Do you have any type of VPN services on your system? I have seen these interfere with connections.

Rick

Hi Ron,

Okay, I wasn't expecting it to not see the ethernet adapter at all.   You have FiOS and network connections in each room and your laptop works immediately, so I'm not sure it's an ISP issue.  I'm doubtful it's specific to that ethernet jack in that room, but just to be thorough have you tried that system on one of the other jacks in your house?

Honestly this is sort of a weird one.  I'm assuming that your internet connection works perfectly fine, speeds are good, etc., once it does connect.  The only real difference seems to be that one system is Win7 (and thus different driver sets) and the other is Win8.1.   

For some reason your NIC isn't being recognized immediately by your system, and Windows isn't even assigning it a generic 169.254 address.  But then it connects.   

The Dell driver for that card should include a diagnostic utility.  Have you tried running that?  Maybe during the time when the system isn't connecting?

Todd

I tried netsh int ip reset resetlog.txt previously and it didn't help.  Don't have a VPN on here.

I think the key issue here is that DHCP isn't seeing the Ethernet card for first few min after booting. Once it connects, I get my full rated speed of 16 Mbps in both directions.

I found a newer NIC driver at the Broadcom site and installed it the other day, but the problem is the same.

I went through the event log at warm reboot and here's the relevant bit: 

• NIC driver initialized successfully at 11:33:00
• NIC configured for full duplex link for 100-Mbps  at 11:33:02
• DHCP Client service entered running state at 11:33:21
• Network Connection service entered running state at 11:33:47
• Network List Service entered the running state at 11:33:47
• Microsoft Network Inspection service entered the running state at 11:33:53
• WinHTTP Web Proxy Auto-Discovery Service entered the running state at 11:34:32
• Browser has forced election on network \Device\NetBT_Tcpip_{8CEE089A-67E9-43A5-974E-8CC76513CE55} because master browser was stopped at 11:35:32
• Computer Browser service was successfully sent a stop control at 11:35:32

So things are happening very quickly. DHCP starts running only 19 sec after the NIC is configured for full duplex. Yet it takes minutes to see any available connections.

I wonder if that Browser forced election and stop ~2 min after the NIC driver starts has anything to do with this. There are quite a few Browser errors in Event Viewer.

Lots of comments about browser forcing elections on the web. Some say it's "normal", others propose all kinds of fixes.  Not sure if it's worth the risk of making things worse by trying some of those fixes.

Am I just beating a dead horse...??

To be honest I'm kind of stumped right now.  I'll reach out to some others that i know and ask for suggestions on what to do.  Maybe they can see something that I'm missing.

Todd

Todd- Thank you, Kind Sir!

I'm stumped too..!

Hi Ron,

To follow up, I haven't been able to locate anyone that can give me any sort of answer on this.  Nobody seems to have a clue what is going on.  Sorry, but I don't think I can help you.

:(

Todd

Todd-

Many thanks for trying. I haven't found a solution either, aside from being patient until it finds an IP address.

another of the mysteries of Microsoft...!