What causes the Ad-Hoc network 'identifying...' 1 minute delay?
I have an ad-hoc network set-up between 2 Windows 7 computers. When I make the connection, the network on both computers is set to 'Identifying....'. This phase last for exactly 1 minute, then the network connects. If I change the ad-hoc network to use Static IP addresses by directly configuring the TCP/IPv4 settings, the network connects straight away. There's no delay. What causes that 1 minute delay, and can it be avoided?
May 17th, 2012 7:32am

Hi, Base on my knowledge, it is normal for two Windows 7 computers using about 1 minute to connect via ad-hoc network. Regards Vincent Wang TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
May 18th, 2012 4:51am

Well, It seems very to me. Why should I, in 2012, have to wait for 1 minute for 2 computers on the same table to communicate with each other? In 1 minute, I can retrieve 1Gb of data from a server on the other side of the world. ... The ad-hoc network connects immediately, if I use static IP Addresses. That is normal to me. I suspect this 1 minute delay is something to do with DHCP or whatever, but I know very little about networking.
May 18th, 2012 10:25am

Still looking for a solution (or an explanation) for this. I want this network to connect instantly, rather than delay for 60 seconds.
Free Windows Admin Tool Kit Click here and download it now
May 22nd, 2012 12:49am

No help then. I thought this would be a simple question to answer.
May 29th, 2012 1:49am

Hi, I would like to explain that An ad hoc network is a temporary connection between computers and devices used for a specific purpose. Peer computers could use DNS dynamic update to register their names, however, very few DNS servers on the Internet support DNS dynamic update. To be successful for peer-to-peer networking, peer computers must not rely on the existing DNS infrastructure. Therefore, there must be a mechanism to resolve peer names to their addresses that does not rely on DNS. For Windows Peer-to-Peer Networking, this mechanism is Peer Name Resolution Protocol (PNRP). So it will take about one minute to connect. For your reference Peer Name Resolution Protocol Regards Vincent Wang TechNet Community Support
Free Windows Admin Tool Kit Click here and download it now
June 1st, 2012 1:42am

Vince, I'm aware that it is a temporary connection. I've googled your explanation, and it's taken word for word from http://technet.microsoft.com/en-us/library/bb457079.aspx Then you've added "So it will take about one minute to connect". There's nothing in your post as evidence, to back up your statement. It's nowhere near good enough to be marked as an answer. There's no causal connection. I repeat - I daily connect to a VPN server located 4,000 miles away. Communication and verification between both servers takes 5 or 6 seconds. So why should an ad hoc network between 2 computers on the same desk take a minute? And note, it's exactly a minute every time. As if it is running this kind of pseudo-code: Do While Time < 1 Minute Attempt to Connect using DNS End Do .... If Not Connected Connect using PNRP EndIf
June 4th, 2012 2:17am

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics