Applies to:

Windows Server 2012

Windows 8

Windows Server 2008 R2

Windows 7

 

Problem description:

Windows 8 RTM, after hibernating, when resuming the system, the connection will be “limited” for around a minute (60 seconds) before it finally connects all the way.

Action Plan:

We had our fellow peer (P1) gather a network trace per my previous post.

Network tracing (packet sniffing) built-in to Windows Server 2008 R2 and Windows Server 2012.
http://blogs.technet.com/b/yongrhee/archive/2012/12/01/network-tracing-packet-sniffing-built-in-to-windows-server-2008-r2-and-windows-server-2012.aspx

Data analysis:

P1 provides the network trace.  And that is it.

Issue:

I don't know what IP address that they got.  ipv4.address==172.x.x.x OR ipv6.address==fe80::x:x:x

What was the timeframe of the 60 seconds that was delayed?

Filtering the network trace.

The first packet with those addresses are:
10:31:17 a.m.
10:43:18 a.m.

Ok, that is 12 minutes with over 90,000 packets.
Talk about finding a needle in the haystack.

The moral of the story is, at a minimum, gather the following data when troubleshooting a network related issue:

IPv4 address:

IPv6 address:

Time (HH:MM:SS):

Ipv4 address of target:

Ipv6 address of target:

Application that is having the problem, and it’s Process ID (PID) from Task Manager:

Network share name that is having the problem:

Website name (if troubleshooting a website/webpage related problem):

Document name (.doc, .docx, .xls, .xlsx, etc…):

Domain name/User name  (if troubleshooting an authentication problem):

DC Ipv4/Ipv6 address:

DHCP Ipv4/Ipv6 address:

DNS Ipv4/Ipv6 address: