Difference in The Behavior of Microsoft Windows Vista Home Premium Between System Booted While Connected To A Network And System Booted Not Connected To A Network
Recently, I have noticed a significant difference in the behavior of the Microsoft Windows Vista Home Premium between the case of the system booted with a connection to a network and the case of the system booted without a connection to a network. My home system hardware consists of a MSI MS-6533E Motherboard computer with an Intel Pentium 4 CPU at 2.4 GHz, 1.5 GB of random access memory, and a fast AGP display processor. The system is constructed so that the slowest part of it, as measured by the Microsoft Windows Vista Performance Index, is the CPU itself with no peripheral "bottle-necks". The following picture shows the operating system background load, as shown by the Microsoft Windows Vista Task Manager, when the system is booted with the external DSL network modem powered down, sometime after the boot. In the first half of the performance chart, the task manager window is minimized, so that its display overhead does not show up. In this case, the system quiescent, averaged, background load is about 3 to 4 percent. The latter half show the background load with the task manager window is fully expanded. The system averaged background load increases to about 5 to 6 percent. The next picture shows the system load when the DSL modem is powered up when the system is in the quiescent state mentioned above. After the process initializations, the system goes into a periodically loaded state, with the load minimum approaching that in the quiescent state as shown above. Due to the number of pictures limitations in one message in this forum, I will continue this message in my first reply to it. -- Yekta
December 3rd, 2011 3:57pm

Sometime later, the system still exhibits the behavior shown in the previous picture. The picture below demonstrates this clearly: The behavior of the system is entirely different when it is booted from the powered down state with the DSL modem already powered up. The following picture illustrates this, some 28 minutes after the boot-up: Note that the system background load has gone way up, with wild oscillations. As before, only the task manager is invoked to monitor the system with no other user task. Again, I will continue this message in my next reply to it, due to the "number of pictures" limitations. -- Yekta
Free Windows Admin Tool Kit Click here and download it now
December 3rd, 2011 4:05pm

The load picture shown just above, is also periodic with the task manager window size. In the next picture, the DSL modem is shut off when the system has been in the "oscillatory" state shown above. The system goes back into its original quiescent state, but it somehow retains the memory of the boot-up with the DSL modem on. The next picture shows what happens when the DSL modem is turned back on: The system somehow has remembered that it has been exhibiting the particular oscillatory behavior, and it starts to go back to it. The last picture, taken sometime after the picture above, and shown in my next reply, illustrates this last point. -- Yekta
December 3rd, 2011 4:17pm

Here is the last picture: The question is: What causes this oscillatory behavior (a significant system load for no reason, it seems) as illustrated above? Is there another system on the network which detects the modem-on boot-up of this system and then causes it to somehow spend more than usual time on a process? -- Yekta
Free Windows Admin Tool Kit Click here and download it now
December 3rd, 2011 4:23pm

Hi, You may make a boot trace to analyse the boot behavior. References: http://www.msfn.org/board/topic/140247-trace-windows-7-bootshutdownhibernatestandbyresume-issues/ Important Note: Microsoft provides third-party contact information to help you find technical support. This contact information may change without notice. Microsoft does not guarantee the accuracy of this third-party contact information. Windows Performance Analysis Tools Sabrina TechNet Community Support
December 5th, 2011 3:35am

Thank you. I have downloaded the recommended software from Microsoft. I will analyze the situation further using these tools and post a report later... -- Yekta
Free Windows Admin Tool Kit Click here and download it now
December 10th, 2011 2:52pm

I have resolved some of the issues I have mentioned above. I have updated the display driver for my SapphireTech/AMD/ATI Radeon HD 3850 AGP Video Graphics Adapter card (see my entry in the Microsoft Internet Explorer 8 and 9 Technet Forum, titled Incompatibility of Microsoft Internet Explorer 9 With The Most Recent AMD/ATI Radeon HD Video Graphics Card Drivers... (url http://social.technet.microsoft.com/Forums/en-US/ieitprocurrentver/thread/b97d85ff-2fd5-4bcb-84f2-7cf60f281577 ). I have then also performed a boot time "CHKDSK" on the boot disk with the "Scan for bad sectors and repair" option which has not found any problems with the disk drive, but it has eliminated a recent complaint from the Windows Update that it has been unable to open a file to decide on the availability of recent updates. After these, the Microsoft Internet Explorer 9 does not function well at all in the system. However, everything else has improved significantly and Mozilla/Firefox Version 8.0.1 works flawlessly. Compare the following task manager output screen picture to the first screen picture shown in my reply above on Saturday, December 03, 2011 9:05 PM. The two screen pictures are taken under the same conditions: The network load on the computer has gone down by an enormous amount. The picture above was taken with the Microsoft Security Essentials active on the taskbar. The next picture shows the case in which the program Microsoft Security Essentials is completely shut down to measure its effect: It does not cause any significant decrease (few percent) in the system performance: I will next trace the "wild oscillations" that has been occurring continuously, should the system boot with the DSL network modem turned on. -- Yekta
December 17th, 2011 3:26pm

Here are the frames of the first 2 seconds of recorded network transactions. For some reason, this forum does not want to post Microsoft Network Analyzer 3.4 output (text), even though the total length of text is far less than 60,000 characters... Frame Time Date Time Offset Process Source Destination Protocol Description Number Local Adjusted Name Name 3 10:05:09 PM 12/21/2011 1737.1446774 192.168.1.254 192.168.1.66 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.66 4 10:05:09 PM 12/21/2011 1737.1547030 192.168.1.254 192.168.1.67 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.67 5 10:05:09 PM 12/21/2011 1737.1646931 192.168.1.254 192.168.1.68 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.68 6 10:05:09 PM 12/21/2011 1737.1746938 192.168.1.254 192.168.1.69 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.69 7 10:05:09 PM 12/21/2011 1737.1846990 192.168.1.254 192.168.1.70 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.70 8 10:05:09 PM 12/21/2011 1737.1947151 192.168.1.254 192.168.1.71 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.71 9 10:05:09 PM 12/21/2011 1737.2046890 192.168.1.254 192.168.1.72 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.72 10 10:05:09 PM 12/21/2011 1737.2147025 192.168.1.254 192.168.1.73 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.73 11 10:05:09 PM 12/21/2011 1737.2246940 192.168.1.254 192.168.1.74 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.74 12 10:05:09 PM 12/21/2011 1737.2347168 192.168.1.254 192.168.1.75 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.75 13 10:05:09 PM 12/21/2011 1737.2446882 192.168.1.254 192.168.1.76 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.76 14 10:05:09 PM 12/21/2011 1737.2547121 192.168.1.254 192.168.1.77 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.77 19 10:05:09 PM 12/21/2011 1737.2647625 192.168.1.254 192.168.1.78 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.78 20 10:05:09 PM 12/21/2011 1737.2747263 192.168.1.254 192.168.1.79 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.79 21 10:05:09 PM 12/21/2011 1737.2847380 192.168.1.254 192.168.1.80 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.80 22 10:05:09 PM 12/21/2011 1737.2947177 192.168.1.254 192.168.1.81 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.81 23 10:05:09 PM 12/21/2011 1737.3047140 192.168.1.254 192.168.1.82 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.82 24 10:05:09 PM 12/21/2011 1737.3147443 192.168.1.254 192.168.1.83 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.83 25 10:05:09 PM 12/21/2011 1737.3247162 192.168.1.254 192.168.1.84 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.84 26 10:05:09 PM 12/21/2011 1737.3347273 192.168.1.254 192.168.1.85 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.85 27 10:05:09 PM 12/21/2011 1737.3447174 192.168.1.254 192.168.1.86 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.86 29 10:05:09 PM 12/21/2011 1737.3547544 192.168.1.254 192.168.1.87 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.87 31 10:05:09 PM 12/21/2011 1737.3647294 192.168.1.254 192.168.1.88 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.88 32 10:05:09 PM 12/21/2011 1737.3747393 192.168.1.254 192.168.1.89 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.89 36 10:05:09 PM 12/21/2011 1737.3847328 192.168.1.254 192.168.1.90 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.90 37 10:05:09 PM 12/21/2011 1737.3947559 192.168.1.254 192.168.1.91 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.91 38 10:05:09 PM 12/21/2011 1737.4047320 192.168.1.254 192.168.1.92 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.92 39 10:05:09 PM 12/21/2011 1737.4147444 192.168.1.254 192.168.1.93 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.93 40 10:05:09 PM 12/21/2011 1737.4247370 192.168.1.254 192.168.1.94 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.94 41 10:05:09 PM 12/21/2011 1737.4347632 192.168.1.254 192.168.1.95 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.95 42 10:05:09 PM 12/21/2011 1737.4447390 192.168.1.254 192.168.1.96 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.96 43 10:05:09 PM 12/21/2011 1737.4547554 192.168.1.254 192.168.1.97 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.97 44 10:05:09 PM 12/21/2011 1737.4647508 192.168.1.254 192.168.1.98 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.98 46 10:05:09 PM 12/21/2011 1737.4747819 192.168.1.254 192.168.1.99 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.99 47 10:05:09 PM 12/21/2011 1737.4847447 192.168.1.254 192.168.1.100 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.100 48 10:05:09 PM 12/21/2011 1737.4947644 192.168.1.254 192.168.1.101 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.101 50 10:05:09 PM 12/21/2011 1737.5049268 192.168.1.254 192.168.1.102 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.102 51 10:05:09 PM 12/21/2011 1737.5148071 192.168.1.254 192.168.1.103 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.103 52 10:05:09 PM 12/21/2011 1737.5247651 192.168.1.254 192.168.1.104 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.104 55 10:05:09 PM 12/21/2011 1737.5347865 192.168.1.254 192.168.1.105 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.105 56 10:05:09 PM 12/21/2011 1737.5447679 192.168.1.254 192.168.1.106 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.106 57 10:05:09 PM 12/21/2011 1737.5548217 192.168.1.254 192.168.1.107 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.107 58 10:05:09 PM 12/21/2011 1737.5647677 192.168.1.254 192.168.1.108 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.108 61 10:05:09 PM 12/21/2011 1737.5747949 192.168.1.254 192.168.1.109 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.109 62 10:05:09 PM 12/21/2011 1737.5847775 192.168.1.254 192.168.1.110 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.110 63 10:05:09 PM 12/21/2011 1737.5948019 192.168.1.254 192.168.1.111 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.111 64 10:05:09 PM 12/21/2011 1737.6047837 192.168.1.254 192.168.1.112 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.112 65 10:05:09 PM 12/21/2011 1737.6148199 192.168.1.254 192.168.1.113 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.113 66 10:05:09 PM 12/21/2011 1737.6247985 192.168.1.254 192.168.1.114 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.114 67 10:05:09 PM 12/21/2011 1737.6348168 192.168.1.254 192.168.1.115 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.115 68 10:05:09 PM 12/21/2011 1737.6447890 192.168.1.254 192.168.1.116 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.116 69 10:05:09 PM 12/21/2011 1737.6548017 192.168.1.254 192.168.1.117 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.117 70 10:05:09 PM 12/21/2011 1737.6647930 192.168.1.254 192.168.1.118 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.118 73 10:05:09 PM 12/21/2011 1737.6748409 192.168.1.254 192.168.1.119 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.119 74 10:05:09 PM 12/21/2011 1737.6847991 192.168.1.254 192.168.1.120 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.120 75 10:05:09 PM 12/21/2011 1737.6948166 192.168.1.254 192.168.1.121 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.121 76 10:05:09 PM 12/21/2011 1737.7048179 192.168.1.254 192.168.1.122 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.122 77 10:05:09 PM 12/21/2011 1737.7148415 192.168.1.254 192.168.1.123 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.123 78 10:05:09 PM 12/21/2011 1737.7248087 192.168.1.254 192.168.1.124 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.124 80 10:05:09 PM 12/21/2011 1737.7348393 192.168.1.254 192.168.1.125 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.125 81 10:05:09 PM 12/21/2011 1737.7448124 192.168.1.254 192.168.1.126 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.126 82 10:05:09 PM 12/21/2011 1737.7548435 192.168.1.254 192.168.1.127 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.127 83 10:05:09 PM 12/21/2011 1737.7648138 192.168.1.254 192.168.1.128 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.128 84 10:05:09 PM 12/21/2011 1737.7748307 192.168.1.254 192.168.1.129 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.129 85 10:05:09 PM 12/21/2011 1737.7848208 192.168.1.254 192.168.1.130 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.130 86 10:05:09 PM 12/21/2011 1737.7948439 192.168.1.254 192.168.1.131 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.131 87 10:05:09 PM 12/21/2011 1737.8048063 192.168.1.254 192.168.1.132 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.132 88 10:05:09 PM 12/21/2011 1737.8148307 192.168.1.254 192.168.1.133 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.133 89 10:05:09 PM 12/21/2011 1737.8248362 192.168.1.254 192.168.1.134 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.134 90 10:05:09 PM 12/21/2011 1737.8348573 192.168.1.254 192.168.1.135 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.135 91 10:05:09 PM 12/21/2011 1737.8448295 192.168.1.254 192.168.1.136 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.136 92 10:05:09 PM 12/21/2011 1737.8548456 192.168.1.254 192.168.1.137 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.137 93 10:05:09 PM 12/21/2011 1737.8648371 192.168.1.254 192.168.1.138 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.138 94 10:05:09 PM 12/21/2011 1737.8671413 YEKTA-NET-PC 192.168.1.254 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.254 95 10:05:09 PM 12/21/2011 1737.8673181 192.168.1.254 YEKTA-NET-PC ARP ARP:Response, 192.168.1.254 at 00-24-37-FF-33-A0 96 10:05:09 PM 12/21/2011 1737.8748680 192.168.1.254 192.168.1.139 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.139 97 10:05:09 PM 12/21/2011 1737.8765506 0.0.0.0 YEKTA-NET-PC ARP ARP:Request, 0.0.0.0 asks for 192.168.1.64 100 10:05:09 PM 12/21/2011 1737.8848620 192.168.1.254 192.168.1.140 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.140 101 10:05:09 PM 12/21/2011 1737.8948728 192.168.1.254 192.168.1.141 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.141 102 10:05:09 PM 12/21/2011 1737.9048704 192.168.1.254 192.168.1.142 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.142 103 10:05:09 PM 12/21/2011 1737.9148817 192.168.1.254 192.168.1.143 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.143 104 10:05:09 PM 12/21/2011 1737.9248514 192.168.1.254 192.168.1.144 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.144 105 10:05:09 PM 12/21/2011 1737.9348684 192.168.1.254 192.168.1.145 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.145 106 10:05:09 PM 12/21/2011 1737.9448621 192.168.1.254 192.168.1.146 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.146 107 10:05:09 PM 12/21/2011 1737.9548818 192.168.1.254 192.168.1.147 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.147 108 10:05:09 PM 12/21/2011 1737.9648557 192.168.1.254 192.168.1.148 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.148 109 10:05:09 PM 12/21/2011 1737.9748746 192.168.1.254 192.168.1.149 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.149 110 10:05:09 PM 12/21/2011 1737.9848658 192.168.1.254 192.168.1.150 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.150 114 10:05:09 PM 12/21/2011 1738.0233813 192.168.1.254 192.168.1.151 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.151 115 10:05:09 PM 12/21/2011 1738.0332915 192.168.1.254 192.168.1.152 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.152 116 10:05:09 PM 12/21/2011 1738.0432542 192.168.1.254 192.168.1.153 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.153 117 10:05:09 PM 12/21/2011 1738.0532999 192.168.1.254 192.168.1.154 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.154 118 10:05:09 PM 12/21/2011 1738.0632523 192.168.1.254 192.168.1.155 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.155 119 10:05:09 PM 12/21/2011 1738.0732843 192.168.1.254 192.168.1.156 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.156 120 10:05:09 PM 12/21/2011 1738.0832621 192.168.1.254 192.168.1.157 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.157 121 10:05:09 PM 12/21/2011 1738.0932997 192.168.1.254 192.168.1.158 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.158 122 10:05:09 PM 12/21/2011 1738.1032643 192.168.1.254 192.168.1.159 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.159 123 10:05:09 PM 12/21/2011 1738.1132812 192.168.1.254 192.168.1.160 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.160 124 10:05:09 PM 12/21/2011 1738.1232781 192.168.1.254 192.168.1.161 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.161 125 10:05:10 PM 12/21/2011 1738.1333053 192.168.1.254 192.168.1.162 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.162 126 10:05:10 PM 12/21/2011 1738.1432691 192.168.1.254 192.168.1.163 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.163 127 10:05:10 PM 12/21/2011 1738.1532894 192.168.1.254 192.168.1.164 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.164 128 10:05:10 PM 12/21/2011 1738.1632840 192.168.1.254 192.168.1.165 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.165 129 10:05:10 PM 12/21/2011 1738.1733051 192.168.1.254 192.168.1.166 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.166 130 10:05:10 PM 12/21/2011 1738.1832781 192.168.1.254 192.168.1.167 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.167 131 10:05:10 PM 12/21/2011 1738.1933255 192.168.1.254 192.168.1.168 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.168 132 10:05:10 PM 12/21/2011 1738.2032916 192.168.1.254 192.168.1.169 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.169 133 10:05:10 PM 12/21/2011 1738.2133205 192.168.1.254 192.168.1.170 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.170 134 10:05:10 PM 12/21/2011 1738.2232955 192.168.1.254 192.168.1.171 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.171 135 10:05:10 PM 12/21/2011 1738.2333177 192.168.1.254 192.168.1.172 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.172 136 10:05:10 PM 12/21/2011 1738.2433534 192.168.1.254 192.168.1.173 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.173 138 10:05:10 PM 12/21/2011 1738.2533432 192.168.1.254 192.168.1.174 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.174 139 10:05:10 PM 12/21/2011 1738.2633028 192.168.1.254 192.168.1.175 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.175 140 10:05:10 PM 12/21/2011 1738.2733253 192.168.1.254 192.168.1.176 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.176 141 10:05:10 PM 12/21/2011 1738.2833640 192.168.1.254 192.168.1.177 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.177 142 10:05:10 PM 12/21/2011 1738.2933390 192.168.1.254 192.168.1.178 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.178 143 10:05:10 PM 12/21/2011 1738.3033465 192.168.1.254 192.168.1.179 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.179 144 10:05:10 PM 12/21/2011 1738.3133329 192.168.1.254 192.168.1.180 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.180 145 10:05:10 PM 12/21/2011 1738.3233543 192.168.1.254 192.168.1.181 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.181 149 10:05:10 PM 12/21/2011 1738.3333757 192.168.1.254 192.168.1.182 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.182 152 10:05:10 PM 12/21/2011 1738.3433460 192.168.1.254 192.168.1.183 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.183 153 10:05:10 PM 12/21/2011 1738.3533391 192.168.1.254 192.168.1.184 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.184 155 10:05:10 PM 12/21/2011 1738.3633382 192.168.1.254 192.168.1.185 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.185 156 10:05:10 PM 12/21/2011 1738.3733573 192.168.1.254 192.168.1.186 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.186 158 10:05:10 PM 12/21/2011 1738.3833536 192.168.1.254 192.168.1.187 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.187 159 10:05:10 PM 12/21/2011 1738.3933459 192.168.1.254 192.168.1.188 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.188 160 10:05:10 PM 12/21/2011 1738.4033466 192.168.1.254 192.168.1.189 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.189 161 10:05:10 PM 12/21/2011 1738.4133621 192.168.1.254 192.168.1.190 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.190 162 10:05:10 PM 12/21/2011 1738.4233422 192.168.1.254 192.168.1.191 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.191 163 10:05:10 PM 12/21/2011 1738.4333717 192.168.1.254 192.168.1.192 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.192 164 10:05:10 PM 12/21/2011 1738.4433497 192.168.1.254 192.168.1.193 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.193 165 10:05:10 PM 12/21/2011 1738.4533770 192.168.1.254 192.168.1.194 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.194 166 10:05:10 PM 12/21/2011 1738.4633498 192.168.1.254 192.168.1.195 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.195 167 10:05:10 PM 12/21/2011 1738.4733684 192.168.1.254 192.168.1.196 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.196 169 10:05:10 PM 12/21/2011 1738.4833693 192.168.1.254 192.168.1.197 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.197 170 10:05:10 PM 12/21/2011 1738.4933843 192.168.1.254 192.168.1.198 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.198 171 10:05:10 PM 12/21/2011 1738.5033576 192.168.1.254 192.168.1.199 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.199 172 10:05:10 PM 12/21/2011 1738.5133771 192.168.1.254 192.168.1.200 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.200 173 10:05:10 PM 12/21/2011 1738.5235747 192.168.1.254 192.168.1.201 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.201 174 10:05:10 PM 12/21/2011 1738.5334081 192.168.1.254 192.168.1.202 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.202 175 10:05:10 PM 12/21/2011 1738.5433717 192.168.1.254 192.168.1.203 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.203 176 10:05:10 PM 12/21/2011 1738.5533914 192.168.1.254 192.168.1.204 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.204 177 10:05:10 PM 12/21/2011 1738.5633736 192.168.1.254 192.168.1.205 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.205 178 10:05:10 PM 12/21/2011 1738.5734009 192.168.1.254 192.168.1.206 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.206 179 10:05:10 PM 12/21/2011 1738.5833768 192.168.1.254 192.168.1.207 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.207 180 10:05:10 PM 12/21/2011 1738.5933934 192.168.1.254 192.168.1.208 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.208 181 10:05:10 PM 12/21/2011 1738.6033812 192.168.1.254 192.168.1.209 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.209 182 10:05:10 PM 12/21/2011 1738.6134191 192.168.1.254 192.168.1.210 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.210 183 10:05:10 PM 12/21/2011 1738.6233877 192.168.1.254 192.168.1.211 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.211 184 10:05:10 PM 12/21/2011 1738.6334029 192.168.1.254 192.168.1.212 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.212 185 10:05:10 PM 12/21/2011 1738.6433905 192.168.1.254 192.168.1.213 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.213 186 10:05:10 PM 12/21/2011 1738.6534334 192.168.1.254 192.168.1.214 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.214 187 10:05:10 PM 12/21/2011 1738.6633947 192.168.1.254 192.168.1.215 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.215 188 10:05:10 PM 12/21/2011 1738.6734125 192.168.1.254 192.168.1.216 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.216 189 10:05:10 PM 12/21/2011 1738.6834406 192.168.1.254 192.168.1.217 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.217 190 10:05:10 PM 12/21/2011 1738.6934282 192.168.1.254 192.168.1.218 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.218 191 10:05:10 PM 12/21/2011 1738.7034160 192.168.1.254 192.168.1.219 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.219 192 10:05:10 PM 12/21/2011 1738.7134265 192.168.1.254 192.168.1.220 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.220 193 10:05:10 PM 12/21/2011 1738.7234107 192.168.1.254 192.168.1.221 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.221 194 10:05:10 PM 12/21/2011 1738.7334433 192.168.1.254 192.168.1.222 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.222 195 10:05:10 PM 12/21/2011 1738.7434138 192.168.1.254 192.168.1.223 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.223 196 10:05:10 PM 12/21/2011 1738.7534285 192.168.1.254 192.168.1.224 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.224 197 10:05:10 PM 12/21/2011 1738.7634130 192.168.1.254 192.168.1.225 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.225 198 10:05:10 PM 12/21/2011 1738.7734517 192.168.1.254 192.168.1.226 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.226 199 10:05:10 PM 12/21/2011 1738.7834217 192.168.1.254 192.168.1.227 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.227 200 10:05:10 PM 12/21/2011 1738.7934414 192.168.1.254 192.168.1.228 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.228 201 10:05:10 PM 12/21/2011 1738.8034259 192.168.1.254 192.168.1.229 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.229 202 10:05:10 PM 12/21/2011 1738.8134538 192.168.1.254 192.168.1.230 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.230 203 10:05:10 PM 12/21/2011 1738.8234265 192.168.1.254 192.168.1.231 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.231 204 10:05:10 PM 12/21/2011 1738.8334479 192.168.1.254 192.168.1.232 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.232 205 10:05:10 PM 12/21/2011 1738.8434400 192.168.1.254 192.168.1.233 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.233 206 10:05:10 PM 12/21/2011 1738.8534644 192.168.1.254 192.168.1.234 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.234 207 10:05:10 PM 12/21/2011 1738.8634400 192.168.1.254 192.168.1.235 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.235 208 10:05:10 PM 12/21/2011 1738.8734569 192.168.1.254 192.168.1.236 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.236 209 10:05:10 PM 12/21/2011 1738.8765294 0.0.0.0 YEKTA-NET-PC ARP ARP:Request, 0.0.0.0 asks for 192.168.1.64 210 10:05:10 PM 12/21/2011 1738.8834557 192.168.1.254 192.168.1.237 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.237 211 10:05:10 PM 12/21/2011 1738.8934673 192.168.1.254 192.168.1.238 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.238 212 10:05:10 PM 12/21/2011 1738.9034540 192.168.1.254 192.168.1.239 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.239 213 10:05:10 PM 12/21/2011 1738.9134654 192.168.1.254 192.168.1.240 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.240 214 10:05:10 PM 12/21/2011 1738.9234549 192.168.1.254 192.168.1.241 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.241 215 10:05:10 PM 12/21/2011 1738.9334933 192.168.1.254 192.168.1.242 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.242 216 10:05:10 PM 12/21/2011 1738.9434577 192.168.1.254 192.168.1.243 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.243 217 10:05:10 PM 12/21/2011 1738.9534788 192.168.1.254 192.168.1.244 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.244 218 10:05:10 PM 12/21/2011 1738.9634628 192.168.1.254 192.168.1.245 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.245 220 10:05:10 PM 12/21/2011 1738.9735660 192.168.1.254 192.168.1.246 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.246 223 10:05:10 PM 12/21/2011 1738.9835139 192.168.1.254 192.168.1.247 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.247 224 10:05:10 PM 12/21/2011 1738.9934702 192.168.1.254 192.168.1.248 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.248 226 10:05:10 PM 12/21/2011 1739.0035081 192.168.1.254 192.168.1.249 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.249 227 10:05:10 PM 12/21/2011 1739.0134926 192.168.1.254 192.168.1.250 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.250 228 10:05:10 PM 12/21/2011 1739.0234950 192.168.1.254 192.168.1.251 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.251 229 10:05:10 PM 12/21/2011 1739.0334820 192.168.1.254 192.168.1.252 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.252 230 10:05:10 PM 12/21/2011 1739.0435093 192.168.1.254 192.168.1.253 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.253 -- Yekta
Free Windows Admin Tool Kit Click here and download it now
December 26th, 2011 2:50am

41 seconds after turn on (10:05:41 12/21/2011), AT and T reaches my home network PC on my private DSL line: Frame Time Date Time Offset Process Source Destination Protocol Description Number Local Adjusted Name Name 1221 10:05:37 PM 12/21/2011 1765.1711367 YEKTA-NET-PC 192.168.1.251 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.251 1222 10:05:37 PM 12/21/2011 1765.1717340 YEKTA-NET-PC 192.168.1.252 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.252 1223 10:05:37 PM 12/21/2011 1765.1722799 YEKTA-NET-PC 192.168.1.253 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.253 1226 10:05:37 PM 12/21/2011 1765.3746928 YEKTA-NET-PC 192.168.1.221 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.221 1227 10:05:37 PM 12/21/2011 1765.3747162 YEKTA-NET-PC 192.168.1.222 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.222 1228 10:05:37 PM 12/21/2011 1765.3747503 YEKTA-NET-PC 192.168.1.223 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.223 1229 10:05:37 PM 12/21/2011 1765.3747623 YEKTA-NET-PC 192.168.1.224 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.224 1230 10:05:37 PM 12/21/2011 1765.3747746 YEKTA-NET-PC 192.168.1.225 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.225 1231 10:05:37 PM 12/21/2011 1765.3747830 YEKTA-NET-PC 192.168.1.226 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.226 1232 10:05:37 PM 12/21/2011 1765.3747914 YEKTA-NET-PC 192.168.1.227 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.227 1233 10:05:37 PM 12/21/2011 1765.3747998 YEKTA-NET-PC 192.168.1.228 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.228 1234 10:05:37 PM 12/21/2011 1765.3748087 YEKTA-NET-PC 192.168.1.229 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.229 1235 10:05:37 PM 12/21/2011 1765.3748171 YEKTA-NET-PC 192.168.1.230 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.230 1236 10:05:37 PM 12/21/2011 1765.3748255 YEKTA-NET-PC 192.168.1.241 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.241 1237 10:05:37 PM 12/21/2011 1765.3748336 YEKTA-NET-PC 192.168.1.242 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.242 1238 10:05:37 PM 12/21/2011 1765.3748419 YEKTA-NET-PC 192.168.1.243 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.243 1239 10:05:37 PM 12/21/2011 1765.3748500 YEKTA-NET-PC 192.168.1.244 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.244 1240 10:05:37 PM 12/21/2011 1765.3748581 YEKTA-NET-PC 192.168.1.245 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.245 1241 10:05:37 PM 12/21/2011 1765.3748665 YEKTA-NET-PC 192.168.1.246 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.246 1242 10:05:37 PM 12/21/2011 1765.3748763 YEKTA-NET-PC 192.168.1.247 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.247 1243 10:05:37 PM 12/21/2011 1765.3748833 YEKTA-NET-PC 192.168.1.248 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.248 1244 10:05:37 PM 12/21/2011 1765.3748903 YEKTA-NET-PC 192.168.1.249 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.249 1245 10:05:37 PM 12/21/2011 1765.3748981 YEKTA-NET-PC 192.168.1.250 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.250 1268 10:05:37 PM 12/21/2011 1765.8746449 YEKTA-NET-PC 192.168.1.231 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.231 1269 10:05:37 PM 12/21/2011 1765.8746680 YEKTA-NET-PC 192.168.1.232 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.232 1270 10:05:37 PM 12/21/2011 1765.8747041 YEKTA-NET-PC 192.168.1.233 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.233 1271 10:05:37 PM 12/21/2011 1765.8747166 YEKTA-NET-PC 192.168.1.234 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.234 1272 10:05:37 PM 12/21/2011 1765.8747287 YEKTA-NET-PC 192.168.1.235 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.235 1273 10:05:37 PM 12/21/2011 1765.8747373 YEKTA-NET-PC 192.168.1.236 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.236 1274 10:05:37 PM 12/21/2011 1765.8747555 YEKTA-NET-PC 192.168.1.237 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.237 1275 10:05:37 PM 12/21/2011 1765.8747647 YEKTA-NET-PC 192.168.1.238 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.238 1276 10:05:37 PM 12/21/2011 1765.8747728 YEKTA-NET-PC 192.168.1.239 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.239 1277 10:05:37 PM 12/21/2011 1765.8747812 YEKTA-NET-PC 192.168.1.240 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.240 1278 10:05:37 PM 12/21/2011 1765.8747898 YEKTA-NET-PC 192.168.1.251 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.251 1279 10:05:37 PM 12/21/2011 1765.8747988 YEKTA-NET-PC 192.168.1.252 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.252 1280 10:05:37 PM 12/21/2011 1765.8748077 YEKTA-NET-PC 192.168.1.253 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.253 1300 10:05:38 PM 12/21/2011 1766.3746143 YEKTA-NET-PC 192.168.1.241 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.241 1301 10:05:38 PM 12/21/2011 1766.3746388 YEKTA-NET-PC 192.168.1.242 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.242 1302 10:05:38 PM 12/21/2011 1766.3746805 YEKTA-NET-PC 192.168.1.243 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.243 1303 10:05:38 PM 12/21/2011 1766.3746922 YEKTA-NET-PC 192.168.1.244 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.244 1304 10:05:38 PM 12/21/2011 1766.3747045 YEKTA-NET-PC 192.168.1.245 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.245 1305 10:05:38 PM 12/21/2011 1766.3747134 YEKTA-NET-PC 192.168.1.246 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.246 1306 10:05:38 PM 12/21/2011 1766.3747218 YEKTA-NET-PC 192.168.1.247 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.247 1307 10:05:38 PM 12/21/2011 1766.3747308 YEKTA-NET-PC 192.168.1.248 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.248 1308 10:05:38 PM 12/21/2011 1766.3747394 YEKTA-NET-PC 192.168.1.249 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.249 1309 10:05:38 PM 12/21/2011 1766.3747484 YEKTA-NET-PC 192.168.1.250 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.250 1314 10:05:38 PM 12/21/2011 1766.8745974 YEKTA-NET-PC 192.168.1.251 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.251 1315 10:05:38 PM 12/21/2011 1766.8746211 YEKTA-NET-PC 192.168.1.252 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.252 1316 10:05:38 PM 12/21/2011 1766.8746571 YEKTA-NET-PC 192.168.1.253 ARP ARP:Request, 192.168.1.64 asks for 192.168.1.253 1350 10:05:41 PM 12/21/2011 1769.2274131 YEKTA-NET-PC 99.56.243.254 ARP ARP:Request, 99.56.242.21 asks for 99.56.243.254 1351 10:05:41 PM 12/21/2011 1769.2276012 99.56.243.254 YEKTA-NET-PC ARP ARP:Response, 99.56.243.254 at 00-24-37-FF-33-A0 1356 10:05:41 PM 12/21/2011 1769.3745648 0.0.0.0 YEKTA-NET-PC ARP ARP:Request, 0.0.0.0 asks for 99.56.242.21 1386 10:05:42 PM 12/21/2011 1770.2905279 YEKTA-NET-PC 99.56.243.254 ARP ARP:Request, 99.56.242.21 asks for 99.56.243.254 1387 10:05:42 PM 12/21/2011 1770.2906989 99.56.243.254 YEKTA-NET-PC ARP ARP:Response, 99.56.243.254 at 00-24-37-FF-33-A0 1388 10:05:42 PM 12/21/2011 1770.3740198 0.0.0.0 YEKTA-NET-PC ARP ARP:Request, 0.0.0.0 asks for 99.56.242.21 1407 10:05:43 PM 12/21/2011 1771.3740058 0.0.0.0 YEKTA-NET-PC ARP ARP:Request, 0.0.0.0 asks for 99.56.242.21 1409 10:05:43 PM 12/21/2011 1771.3895651 192.168.1.254 192.168.1.1 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.1 1411 10:05:43 PM 12/21/2011 1771.3901705 192.168.1.254 192.168.1.2 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.2 1413 10:05:43 PM 12/21/2011 1771.3907901 192.168.1.254 192.168.1.3 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.3 1415 10:05:43 PM 12/21/2011 1771.3914572 192.168.1.254 192.168.1.4 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.4 1446 10:05:44 PM 12/21/2011 1772.9026359 192.168.1.254 192.168.1.1 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.1 1448 10:05:44 PM 12/21/2011 1772.9031650 192.168.1.254 192.168.1.2 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.2 1450 10:05:44 PM 12/21/2011 1772.9037642 192.168.1.254 192.168.1.3 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.3 1452 10:05:44 PM 12/21/2011 1772.9043685 192.168.1.254 192.168.1.4 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.4 1454 10:05:44 PM 12/21/2011 1772.9050283 192.168.1.254 192.168.1.5 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.5 1456 10:05:44 PM 12/21/2011 1772.9056564 192.168.1.254 192.168.1.6 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.6 1458 10:05:44 PM 12/21/2011 1772.9065322 192.168.1.254 192.168.1.7 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.7 1460 10:05:44 PM 12/21/2011 1772.9071954 192.168.1.254 192.168.1.8 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.8 1462 10:05:44 PM 12/21/2011 1772.9078298 192.168.1.254 192.168.1.9 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.9 1464 10:05:44 PM 12/21/2011 1772.9086878 192.168.1.254 192.168.1.10 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.10 1508 10:05:47 PM 12/21/2011 1776.0479879 192.168.1.254 192.168.1.11 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.11 1510 10:05:47 PM 12/21/2011 1776.0486072 192.168.1.254 192.168.1.12 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.12 1512 10:05:47 PM 12/21/2011 1776.0491944 192.168.1.254 192.168.1.13 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.13 1514 10:05:47 PM 12/21/2011 1776.0498806 192.168.1.254 192.168.1.14 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.14 1516 10:05:47 PM 12/21/2011 1776.0506723 192.168.1.254 192.168.1.15 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.15 1518 10:05:47 PM 12/21/2011 1776.0512989 192.168.1.254 192.168.1.16 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.16 1520 10:05:47 PM 12/21/2011 1776.0519247 192.168.1.254 192.168.1.17 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.17 1522 10:05:47 PM 12/21/2011 1776.0525331 192.168.1.254 192.168.1.18 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.18 1524 10:05:47 PM 12/21/2011 1776.0531994 192.168.1.254 192.168.1.19 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.19 -- Yekta
December 26th, 2011 2:58am

Here is the number of 192.168.xxx.xxx frames between two AT and T negotiation frames: Frame Time Date Time Offset Process Source Destination Protocol Description Number Local Adjusted Name Name 2017 10:06:09 PM 12/21/2011 1797.6012158 YEKTA-NET-PC 99.56.243.254 ARP ARP:Request, 99.56.242.21 asks for 99.56.243.254 2018 10:06:09 PM 12/21/2011 1797.6014108 99.56.243.254 YEKTA-NET-PC ARP ARP:Response, 99.56.243.254 at 00-24-37-FF-33-A0 2022 10:06:10 PM 12/21/2011 1798.4901813 192.168.1.254 192.168.1.121 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.121 2024 10:06:10 PM 12/21/2011 1798.4907174 192.168.1.254 192.168.1.122 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.122 2026 10:06:10 PM 12/21/2011 1798.4913440 192.168.1.254 192.168.1.123 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.123 2028 10:06:10 PM 12/21/2011 1798.4920069 192.168.1.254 192.168.1.124 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.124 2030 10:06:10 PM 12/21/2011 1798.4925969 192.168.1.254 192.168.1.125 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.125 2032 10:06:10 PM 12/21/2011 1798.4932671 192.168.1.254 192.168.1.126 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.126 2034 10:06:10 PM 12/21/2011 1798.4938921 192.168.1.254 192.168.1.127 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.127 2036 10:06:10 PM 12/21/2011 1798.4945625 192.168.1.254 192.168.1.128 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.128 2038 10:06:10 PM 12/21/2011 1798.4952347 192.168.1.254 192.168.1.129 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.129 2040 10:06:10 PM 12/21/2011 1798.4960429 192.168.1.254 192.168.1.130 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.130 2043 10:06:10 PM 12/21/2011 1799.0388719 192.168.1.254 192.168.1.131 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.131 2045 10:06:10 PM 12/21/2011 1799.0394122 192.168.1.254 192.168.1.132 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.132 2047 10:06:10 PM 12/21/2011 1799.0402677 192.168.1.254 192.168.1.133 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.133 2049 10:06:10 PM 12/21/2011 1799.0409007 192.168.1.254 192.168.1.134 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.134 2051 10:06:10 PM 12/21/2011 1799.0415136 192.168.1.254 192.168.1.135 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.135 2053 10:06:10 PM 12/21/2011 1799.0421930 192.168.1.254 192.168.1.136 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.136 2055 10:06:10 PM 12/21/2011 1799.0427473 192.168.1.254 192.168.1.137 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.137 2057 10:06:10 PM 12/21/2011 1799.0434340 192.168.1.254 192.168.1.138 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.138 2059 10:06:10 PM 12/21/2011 1799.0440589 192.168.1.254 192.168.1.139 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.139 2061 10:06:10 PM 12/21/2011 1799.0446861 192.168.1.254 192.168.1.140 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.140 2063 10:06:11 PM 12/21/2011 1799.5162994 192.168.1.254 192.168.1.141 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.141 2065 10:06:11 PM 12/21/2011 1799.5168888 192.168.1.254 192.168.1.142 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.142 2067 10:06:11 PM 12/21/2011 1799.5175124 192.168.1.254 192.168.1.143 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.143 2069 10:06:11 PM 12/21/2011 1799.5189525 192.168.1.254 192.168.1.144 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.144 2071 10:06:11 PM 12/21/2011 1799.5196448 192.168.1.254 192.168.1.145 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.145 2073 10:06:11 PM 12/21/2011 1799.5204485 192.168.1.254 192.168.1.146 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.146 2075 10:06:11 PM 12/21/2011 1799.5210707 192.168.1.254 192.168.1.147 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.147 2077 10:06:11 PM 12/21/2011 1799.5216942 192.168.1.254 192.168.1.148 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.148 2079 10:06:11 PM 12/21/2011 1799.5223733 192.168.1.254 192.168.1.149 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.149 2081 10:06:11 PM 12/21/2011 1799.5229287 192.168.1.254 192.168.1.150 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.150 2132 10:06:13 PM 12/21/2011 1801.5202561 192.168.1.254 192.168.1.151 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.151 2134 10:06:13 PM 12/21/2011 1801.5207975 192.168.1.254 192.168.1.152 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.152 2136 10:06:13 PM 12/21/2011 1801.5213998 192.168.1.254 192.168.1.153 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.153 2138 10:06:13 PM 12/21/2011 1801.5220912 192.168.1.254 192.168.1.154 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.154 2140 10:06:13 PM 12/21/2011 1801.5227195 192.168.1.254 192.168.1.155 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.155 2142 10:06:13 PM 12/21/2011 1801.5233221 192.168.1.254 192.168.1.156 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.156 2144 10:06:13 PM 12/21/2011 1801.5240984 192.168.1.254 192.168.1.157 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.157 2146 10:06:13 PM 12/21/2011 1801.5247323 192.168.1.254 192.168.1.158 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.158 2148 10:06:13 PM 12/21/2011 1801.5253534 192.168.1.254 192.168.1.159 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.159 2150 10:06:13 PM 12/21/2011 1801.5260160 192.168.1.254 192.168.1.160 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.160 2155 10:06:13 PM 12/21/2011 1802.0884847 192.168.1.254 192.168.1.161 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.161 2157 10:06:13 PM 12/21/2011 1802.0890476 192.168.1.254 192.168.1.162 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.162 2159 10:06:13 PM 12/21/2011 1802.0896541 192.168.1.254 192.168.1.163 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.163 2161 10:06:13 PM 12/21/2011 1802.0903380 192.168.1.254 192.168.1.164 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.164 2163 10:06:13 PM 12/21/2011 1802.0909691 192.168.1.254 192.168.1.165 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.165 2165 10:06:13 PM 12/21/2011 1802.0916345 192.168.1.254 192.168.1.166 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.166 2167 10:06:13 PM 12/21/2011 1802.0923774 192.168.1.254 192.168.1.167 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.167 2169 10:06:13 PM 12/21/2011 1802.0929227 192.168.1.254 192.168.1.168 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.168 2171 10:06:13 PM 12/21/2011 1802.0935770 192.168.1.254 192.168.1.169 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.169 2173 10:06:13 PM 12/21/2011 1802.0946235 192.168.1.254 192.168.1.170 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.170 2177 10:06:14 PM 12/21/2011 1802.5629419 192.168.1.254 192.168.1.171 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.171 2179 10:06:14 PM 12/21/2011 1802.5646139 192.168.1.254 192.168.1.172 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.172 2181 10:06:14 PM 12/21/2011 1802.5652612 192.168.1.254 192.168.1.173 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.173 2183 10:06:14 PM 12/21/2011 1802.5658923 192.168.1.254 192.168.1.174 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.174 2185 10:06:14 PM 12/21/2011 1802.5665061 192.168.1.254 192.168.1.175 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.175 2187 10:06:14 PM 12/21/2011 1802.5672858 192.168.1.254 192.168.1.176 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.176 2189 10:06:14 PM 12/21/2011 1802.5679333 192.168.1.254 192.168.1.177 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.177 2191 10:06:14 PM 12/21/2011 1802.5685544 192.168.1.254 192.168.1.178 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.178 2193 10:06:14 PM 12/21/2011 1802.5691648 192.168.1.254 192.168.1.179 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.179 2195 10:06:14 PM 12/21/2011 1802.5697769 192.168.1.254 192.168.1.180 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.180 2200 10:06:14 PM 12/21/2011 1803.0816366 192.168.1.254 192.168.1.181 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.181 2202 10:06:14 PM 12/21/2011 1803.0822051 192.168.1.254 192.168.1.182 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.182 2204 10:06:14 PM 12/21/2011 1803.0828957 192.168.1.254 192.168.1.183 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.183 2206 10:06:14 PM 12/21/2011 1803.0835707 192.168.1.254 192.168.1.184 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.184 2208 10:06:14 PM 12/21/2011 1803.0842009 192.168.1.254 192.168.1.185 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.185 2210 10:06:14 PM 12/21/2011 1803.0848138 192.168.1.254 192.168.1.186 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.186 2212 10:06:14 PM 12/21/2011 1803.0854371 192.168.1.254 192.168.1.187 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.187 2214 10:06:14 PM 12/21/2011 1803.0860679 192.168.1.254 192.168.1.188 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.188 2218 10:06:14 PM 12/21/2011 1803.0879830 192.168.1.254 192.168.1.189 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.189 2220 10:06:14 PM 12/21/2011 1803.0885911 192.168.1.254 192.168.1.190 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.190 2224 10:06:15 PM 12/21/2011 1803.5868587 192.168.1.254 192.168.1.191 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.191 2226 10:06:15 PM 12/21/2011 1803.5874842 192.168.1.254 192.168.1.192 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.192 2228 10:06:15 PM 12/21/2011 1803.5881334 192.168.1.254 192.168.1.193 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.193 2230 10:06:15 PM 12/21/2011 1803.5887522 192.168.1.254 192.168.1.194 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.194 2232 10:06:15 PM 12/21/2011 1803.5893964 192.168.1.254 192.168.1.195 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.195 2234 10:06:15 PM 12/21/2011 1803.5901247 192.168.1.254 192.168.1.196 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.196 2236 10:06:15 PM 12/21/2011 1803.5907698 192.168.1.254 192.168.1.197 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.197 2238 10:06:15 PM 12/21/2011 1803.5915461 192.168.1.254 192.168.1.198 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.198 2240 10:06:15 PM 12/21/2011 1803.5924650 192.168.1.254 192.168.1.199 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.199 2242 10:06:15 PM 12/21/2011 1803.5933788 192.168.1.254 192.168.1.200 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.200 2259 10:06:15 PM 12/21/2011 1804.0905062 192.168.1.254 192.168.1.201 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.201 2261 10:06:15 PM 12/21/2011 1804.0911004 192.168.1.254 192.168.1.202 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.202 2263 10:06:15 PM 12/21/2011 1804.0917130 192.168.1.254 192.168.1.203 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.203 2265 10:06:15 PM 12/21/2011 1804.0928724 192.168.1.254 192.168.1.204 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.204 2267 10:06:15 PM 12/21/2011 1804.0934323 192.168.1.254 192.168.1.205 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.205 2269 10:06:15 PM 12/21/2011 1804.0942067 192.168.1.254 192.168.1.206 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.206 2271 10:06:15 PM 12/21/2011 1804.0948861 192.168.1.254 192.168.1.207 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.207 2273 10:06:15 PM 12/21/2011 1804.0956831 192.168.1.254 192.168.1.208 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.208 2275 10:06:15 PM 12/21/2011 1804.0963983 192.168.1.254 192.168.1.209 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.209 2277 10:06:15 PM 12/21/2011 1804.0970581 192.168.1.254 192.168.1.210 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.210 2279 10:06:16 PM 12/21/2011 1804.3425617 192.168.1.254 YEKTA-NET-PC ARP ARP:Request, 192.168.1.254 asks for 192.168.1.64 2290 10:06:16 PM 12/21/2011 1804.5943775 192.168.1.254 192.168.1.211 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.211 2292 10:06:16 PM 12/21/2011 1804.5948932 192.168.1.254 192.168.1.212 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.212 2294 10:06:16 PM 12/21/2011 1804.5956908 192.168.1.254 192.168.1.213 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.213 2296 10:06:16 PM 12/21/2011 1804.5963579 192.168.1.254 192.168.1.214 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.214 2298 10:06:16 PM 12/21/2011 1804.5969781 192.168.1.254 192.168.1.215 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.215 2300 10:06:16 PM 12/21/2011 1804.5975882 192.168.1.254 192.168.1.216 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.216 2302 10:06:16 PM 12/21/2011 1804.5982003 192.168.1.254 192.168.1.217 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.217 2304 10:06:16 PM 12/21/2011 1804.5988535 192.168.1.254 192.168.1.218 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.218 2306 10:06:16 PM 12/21/2011 1804.5996069 192.168.1.254 192.168.1.219 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.219 2308 10:06:16 PM 12/21/2011 1804.6002400 192.168.1.254 192.168.1.220 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.220 2317 10:06:16 PM 12/21/2011 1805.0987089 192.168.1.254 192.168.1.221 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.221 2319 10:06:16 PM 12/21/2011 1805.0992637 192.168.1.254 192.168.1.222 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.222 2321 10:06:16 PM 12/21/2011 1805.0998755 192.168.1.254 192.168.1.223 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.223 2323 10:06:16 PM 12/21/2011 1805.1004776 192.168.1.254 192.168.1.224 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.224 2325 10:06:16 PM 12/21/2011 1805.1011056 192.168.1.254 192.168.1.225 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.225 2327 10:06:16 PM 12/21/2011 1805.1017241 192.168.1.254 192.168.1.226 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.226 2329 10:06:16 PM 12/21/2011 1805.1023387 192.168.1.254 192.168.1.227 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.227 2331 10:06:16 PM 12/21/2011 1805.1032209 192.168.1.254 192.168.1.228 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.228 2333 10:06:16 PM 12/21/2011 1805.1038696 192.168.1.254 192.168.1.229 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.229 2335 10:06:16 PM 12/21/2011 1805.1044879 192.168.1.254 192.168.1.230 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.230 2340 10:06:17 PM 12/21/2011 1805.6033135 192.168.1.254 192.168.1.231 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.231 2342 10:06:17 PM 12/21/2011 1805.6038270 192.168.1.254 192.168.1.232 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.232 2344 10:06:17 PM 12/21/2011 1805.6044416 192.168.1.254 192.168.1.233 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.233 2346 10:06:17 PM 12/21/2011 1805.6050998 192.168.1.254 192.168.1.234 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.234 2348 10:06:17 PM 12/21/2011 1805.6057588 192.168.1.254 192.168.1.235 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.235 2350 10:06:17 PM 12/21/2011 1805.6063807 192.168.1.254 192.168.1.236 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.236 2352 10:06:17 PM 12/21/2011 1805.6071545 192.168.1.254 192.168.1.237 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.237 2354 10:06:17 PM 12/21/2011 1805.6080817 192.168.1.254 192.168.1.238 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.238 2356 10:06:17 PM 12/21/2011 1805.6087290 192.168.1.254 192.168.1.239 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.239 2358 10:06:17 PM 12/21/2011 1805.6093448 192.168.1.254 192.168.1.240 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.240 2365 10:06:17 PM 12/21/2011 1806.1078757 192.168.1.254 192.168.1.241 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.241 2367 10:06:17 PM 12/21/2011 1806.1084786 192.168.1.254 192.168.1.242 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.242 2369 10:06:17 PM 12/21/2011 1806.1091633 192.168.1.254 192.168.1.243 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.243 2371 10:06:17 PM 12/21/2011 1806.1098349 192.168.1.254 192.168.1.244 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.244 2373 10:06:17 PM 12/21/2011 1806.1104570 192.168.1.254 192.168.1.245 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.245 2375 10:06:17 PM 12/21/2011 1806.1112471 192.168.1.254 192.168.1.246 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.246 2377 10:06:17 PM 12/21/2011 1806.1118810 192.168.1.254 192.168.1.247 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.247 2379 10:06:17 PM 12/21/2011 1806.1125372 192.168.1.254 192.168.1.248 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.248 2381 10:06:17 PM 12/21/2011 1806.1131521 192.168.1.254 192.168.1.249 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.249 2383 10:06:17 PM 12/21/2011 1806.1138167 192.168.1.254 192.168.1.250 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.250 2387 10:06:18 PM 12/21/2011 1806.6103767 192.168.1.254 192.168.1.251 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.251 2389 10:06:18 PM 12/21/2011 1806.6109687 192.168.1.254 192.168.1.252 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.252 2391 10:06:18 PM 12/21/2011 1806.6116540 192.168.1.254 192.168.1.253 ARP ARP:Request, 192.168.1.254 asks for 192.168.1.253 2589 10:06:45 PM 12/21/2011 1833.3701474 YEKTA-NET-PC 99.56.243.254 ARP ARP:Request, 99.56.242.21 asks for 99.56.243.254 2590 10:06:45 PM 12/21/2011 1833.3703371 99.56.243.254 YEKTA-NET-PC ARP ARP:Response, 99.56.243.254 at 00-24-37-FF-33-A0 -- Yekta
Free Windows Admin Tool Kit Click here and download it now
December 26th, 2011 3:05am

And finally, the Microsoft Windows Vista Task Manager, Performance charts during all of this: The first chart shows the DSL modem turn on transition at 10:05:00 PM 12/21/2011. The second chart ends at 10:28:00 PM 12/21/2011. -- Yekta
December 26th, 2011 3:11am

One of the recurring questions about the system I have been using is: How fast is this system, really? Instead of giving numbers measured in "flops" which relate to the raw system performance in integer or in floating point arithmetic, I have decided to give an example which is more relevant to the use of the system. The following picture shows the entire display screen (1280x1024x32) of the computer, with the computer running three independent, display and computation intensive programs at the same time. The top half of the screen shows a depiction of an aquarium with 30 fish in it. The aquarium is larger than what is shown on the display, so the display pans slowly from side to side to cover the entire aquarium. The fish move very smoothly in all orientations, as well as the clock display, the aerator bubbles, the lighting changes due to the water ripples on the surface, and some of the water "plants". The frame rate of this program while running alone and covering the entire 1280x1024x32 display is about 80 full frames per second on the average. The lower right corner of the display shows a particular layout on the opening screen of Hoyle's Mega Mahjongg puzzle. The layout continuously and relatively smoothly rotates around its vertical axis while assembling and then subsequently dis-assembling itself, before a new layout appears, and goes through the same cycle. In the meantime, many lighted sticks (green fuzzy balls) and wing-flapping butterflies fly randomly over the rotating layout. The lower left corner of the screen is occupied by the older version of the aquarium program with seven fish in it, with animated bubbles, lighting, and clock/calendar. Its fixed display gets about two to three frames per second update rate before the CPU reaches the 100 percent load limit, with all three programs running simultaneously. The system can maintain this display with the CPU at the 100 percent load indefinitely, as long as the DSL modem is off. Anything that comes from the network is easily visible with the changing frame rates. -- Yekta
Free Windows Admin Tool Kit Click here and download it now
December 27th, 2011 1:22am

I have further analyzed the problem, and I have found out that IPv4 DHCP server and IPv4 DNS server addresses in my pc was being set remotely to the rogue network addresses 192.168.xxx.xxx . This type of generic network address is only used in completely isolated clusters with no outside connections, definitely not used on a single computer on a single DSL direct line modem. The following two pictures of the Microsoft Windows Vista Network Details display illustrate this: The next reply will show two more of the parameters display pictures, due to the number of pictures limitations in one message... -- Yekta
January 11th, 2012 11:39am

Here are the next two network parameter displays: My next reply shows an AT&T (!?) e-mail I have received this morning, asking me for my e-mail password (!?), among other things, to see whether I have been using my e-mail account (!?). This is completely contrary to the DSL leased line agreement I have been paying for nearly three years. I have not called them yet. -- Yekta
Free Windows Admin Tool Kit Click here and download it now
January 11th, 2012 11:44am

Here is the nothing-less-than-amazing AT&T e-mail: I am looking into this further... -- Yekta
January 11th, 2012 11:46am

I have looked at the actual text (transmitted form of the e-mail) of the "at&t" e-mail shown in my previous reply, and I have noticed that it is coming from an unknown cluster through "Students.CSN.edu", which is a "College Of Southern Nevada" computer supposedly for their students. Any access to this site indicates that it is not a trustable site to even connect to. Below is the entire header and the body of the message shown as pictures to prevent dissemination: My next reply shows the rest of the message, and I'll let you know what happened when I have called AT and T. -- Yekta
Free Windows Admin Tool Kit Click here and download it now
January 12th, 2012 1:34pm

Here is the rest of that message: I then called the AT &T and told the agent on the phone about this message. He told me not to reply to it, and gave me an AT&T e-mail address to forward it to. I did this while he was on the phone. This agent did seem to know about the details of the network, so I mentioned to him what was happening on my DSL line. I told him about the rogue network assignment first. He asked about the modem gateway type and after I told him, he thought that the modem was a wireless one. I assured him (by reading the light designations on the modem) that there is no wireless anything on my computer. In fact, I do not use any wireless computer connections in my house. He found this hard to believe and ran some tests verifying every IP setting I have read to him from my computer. I told him that DHCP server and DNS server on my computer should not be set to 192.168.1.254, as the computer is directly connected to outside. Network 192, subnet 168 is a completely isolated cluster address range, which should not be on the global internet for any extended period of time. In fact, for the duration it is on the global internet, it will cause protocol violations. The agent run tests and I talked to him for about 45 minutes. Then, right in the middle of the tests, after I told him that I was directly seeing the rogue assignment first, and then about 40 seconds later, AT and T IP addresses came in. He hung up for mysterious reasons without saying anything more. The next call resulted in another agent answering the phone and not knowing what the previous one has been doing. I told the next agent to tell the previous one to call me as soon as possible. -- Yekta
January 12th, 2012 1:53pm

Here is the CSN, which is a genuine school as far as I can tell: -- Yekta
Free Windows Admin Tool Kit Click here and download it now
January 12th, 2012 1:55pm

After receiving several more of the "AT&T" team messages (one came in yesterday, March 05, 2012, see first picture below), I also received one which was apparently filled in by somebody else. The real AT and T has supplied an e-mail address to turn those in, as they come in. I then came across a news item about banking, with a very similar scam. The item is shown in the second picture. -- Yekta
March 7th, 2012 1:53am

Hi Yekta, reads like a novel... Can you open a command prompt (Start->All Programs->Accessories->Command Prompt) and type in : ipconfig /all (note the space before the slash) and then press Enter. Please post screenshot. My modem has two IP addresses - one for the internet side (WAN) of itself and one for my side (LAN). The second one starts with 192.168.x.x. These 192.168 addresses are called 'non-routable' ip addresses, that is they cannot be routed over the internet. My computer also has a 192.168.x.x ip address. It is up to my modem to perform address translation for all info passing through it. This is for my protection. It stops my computer from being "seen" on the internet (and then hacked very very quickly) It is possible to disable this in the settings of my modem by disabling something like "Network Address Translation" but I would advise against this and I would check through the settings of your modem to ensure you have not done this because it appears your PC does have a routable address which could be very bad for you. So, when I switch my modem on it gets WAN (internet) IP address from my ISP's DHCP server but then it has it's own built in DHCP server which it then uses to assign IP addresses to all my connected computers. These addresses all start with 192.168.x.x Say my computer is assigned 192.168.0.2 and my modem's LAN address is 192.168.0.1, then my computer should see dhcp server at 192.168.0.1 " " " " dns server at 192.168.0.1 " " " " default gateway at 192.168.0.1 There are three classes of non-routable addresses - 192.168.x.x is generally used for the smallest networks. Remember, it is in your interest for your PC to be using a non-routable ip address. Just out of curiousity, did someone else configure your modem or set up your internet connection for you? If so think about finding the factory reset button on the modem and using the cd/dvd that came with the modem to reset everything, including new passwords. Maybe even call a support rep to help with this... Also please think of obtaining a webmail account and redirecting existing e-mail to it. I use gmail and it has excellent spam filtering. You should not even open those emails... General rule of thumb is to only use your primary e-mail address to set up other email accounts.
Free Windows Admin Tool Kit Click here and download it now
March 10th, 2012 10:46pm

It is nice to hear from someone who likes my prose, and thank you for the pointers. I was very busy in flight training, becoming a flight instructor. I did not have any time to monitor the forums. The modem I have is one of the simplest and cheapest DSL modems one can buy and it is about three and a half years old. It only allows only one connection to a single computer, and it would not connect to a network hub or to a network switch. Resetting the modem does not help the matter. One very sure way to isolate a computer from the external network is to use one computer with two network cards as the network interface computer. One of the network cards is connected to the simple and cheap modem, and through it to the external network. The other network card drives, what one might call, an in-house isolated network which can have any number of other computers, network hubs and network switches. One can turn on and off any kind of packet forwarding between the two network cards depending on the degree of isolation you desire. It is like having a super-smart modem, at no added cost, should you have an old computer you can use for this purpose. Another nice feature is the fact that the newer network cards work much better on even the old computers with simple DSL modems. I'll check on the points you have made and post the results subsequently... -- Yekta
September 13th, 2012 10:33pm

I graduated to become a Certified Flight Instructor ASE, AME, IA on September 24, 2012. I finally had some time to resolve the original problem I had run into, as illustrated in my starting message dated December 3, 2011 above. In the mean time, my network supplier AT and T had raised the cost of the network connection to nearly twice what it was before as their initial two year offer had ran through its course. I chose the lower speed option to hold the cost about the same as it was before. With the lower speed network, the load on the CPU stayed the same, going up to 100 percent in pulses as I had shown before. This was utterly ridiculous. I know, in detail, that the hardware is built in such a way not to exhibit any such behavior. The Microsoft Windows Vista Home Premium, as I had shown above, was not the cause of this behavior either. Yesterday, the regular Microsoft Windows Update notice came in with their latest bug fixes to the operating system. The network load took much longer time than expected due to the pulsing behavior. I decided to fix this problem once and for all, right there. The network interface chip on the motherboard of this computer is a Realtek RTL 8139. I have used this chip in many different places under many different configurations and under different operating systems for about than 10 years. It is a very fine chip that works very well. I also know that the motherboard architecture is also arranged correctly to accommodate this chip. To make sure that there is nothing broken in the motherboard LAN interface, I shut the on board LAN adapter chip down in the BIOS set up, installed a Realtek RTL 8169 PCI Gigabit LAN adapter in the one unused PCI slot in the computer, and booted the computer back up. The Microsoft Windows Vista recognized the new card and installed the driver for it. It also offered an update to the new driver. I installed the new update, and then rebooted the computer again. The network connected through the DSL modem as it did before, with exactly the same pulsing behavior. So, the hardware, as I had predicted, was never at fault. I left the new card in place, as it had the faster and better chip for future use on it. At this time, some part of some software in the computer, addressing the network interface was almost surely causing the problem. Almost surely, as the problem could be caused by another remote system somehow addressing the DSL modem externally, as I had indicated in my previous messages. I decided to use the AT&T Troubleshoot & Resolve Tool, initially supplied on a CD ROM when I bought my DSL modem from AT&T, and later updated regularly through its own update option from the AT&T Web server. The tool (Version 2011) came up and went through its usual steps as I had shown in my previous messages. It showed nothing different than I had encountered before. I decided to go through all of its options to make sure nothing else had changed in its "world" of software. Everything worked until I asked it to check the computer system and the e-mail settings. Before it checked those, it checked with AT&T Web Server to see whether there was an update to itself. It found a new version (AT&T Troubleshoot & Resolve Tool Version 2012) of itself and proceeded to install it. It went through 99 percent of the installation and it got stuck at the end of it for about 40 minutes. It then came back with an error message that the installation stream was interrupted due to erroneous remote server behavior, and asked me to contact AT&T. I contacted the AT&T service through their Web chat option. I filled the Web chat form with the detailed description of the problem. An operator connected and after verifying account information, asked me whether my e-mail and network connections were working well. They were working well, and I told her so. She told me then to ignore the AT&T Troubleshoot & Resolve Tool message. I told her that that would be easy, but how could I then get the updates to the AT&T Troubleshoot & Resolve Tool as the update procedure crashed with the same message every time? She finally saw what I was getting at, and suggested that I read an online article about updating the Tool and that I could download the AT&T Troubleshoot & Resolve Tool separately from their Web server. She typed in a live link to the article, and we disconnected after I told her that I did not need anything else. The live link however, sent me to a web page "article not found" error, and then directed me to a questionnaire. I skipped the questionnaire about the service at this time, and "saved" the printed chat dialogue using the "chat" Tool's "Save" option. It printed a message stating that the typed contents were copied to the clipboard and I could then paste the clipboard contents anywhere I wanted. I exited the chat tool, opened the "Notepad" and tried to paste, only to find that nothing was in the clipboard. Well, I was still determined to solve the original problem. Undaunted, I went to the AT&T Web server and after a short search located a downloadable version of the AT&T Troubleshoot & Resolve Tool Version 2012 for DSL. It downloaded a small downloader for the real Tool. At this point, not wanting to miss even a transient event, I opened the Microsoft Windows Vista Task Manager, and set it to "Performance" display. I then ran the small downloader for the Tool on my machine. It came up with a small display advising me to wait and the Task manager CPU display showing the huge network pulses normally got even busier. The downloader checked the accounting details, machine suitability, and the proceeded to look for a previous version of the Tool before it updated it. It surely did find the AT&T Troubleshoot & Resolve Tool Version 2011 on the machine. It then advised me to use the "Update" command in that existing version 2011 of the AT&T Troubleshoot & Resolve Tool on the machine to accomplish the update. The only other option it offered was the "Exit" button from the downloader for the new version. At this point, probably anyone else in my position at the keyboard would have "detonated" was my feeling, but I was used to encountering complete non-working cycles like this. I chose the only way out of the downloader by mouse-clicking the "Exit" button and I noted that the downloader did something entirely unexpected, on the Task Manager Performance CPU display: It somehow shut the huge network pulses down completely. With the network connected, and e-mail and web access completely working, there were no more large network related load pulses. I concluded that all previous versions of the AT&T Troubleshoot & Resolve Tool were the cause of those network related load pulses, although none of their processes appear in the Task Manager Processes or Services Tables. Presently, with all of its previous versions buggy in the way described above and the its update loop completely useless, the AT&T Troubleshoot & Resolve Tool Version 2011 somehow pointed to itself as the culprit in a most indirect way. I decided to uninstall it. It did uninstall using its Uninstall utility in the Programs Section of the Control Panel. I verified that the network load pulses no longer appeared even after a complete shutdown and reboot, as long as the AT&T Troubleshoot & Resolve Tool Version 2011 was not installed into the system. Now, I had to get the AT&T Troubleshoot & Resolve Tool Version 2012 into the system. I again downloaded the downloader for it making sure that none of those odd network related load pulses appear again. I ran it again, and after going through the steps mentioned above, it asked for AT&T network membership password, and then proceeded to install the Version 2012 one piece at a time through the network. It took a long time to do this, but it managed to completely install it. And, after a reboot, it did what I exactly did not want it to do: It brought the network related load pulses back. The culprit was now totally identified. The AT&T Troubleshoot & Resolve Tool was somehow always running continuously when I did not want it to run at all. I noted the two small AT&T icons on the right side of the standard bottom taskbar, and sure enough they were the AT&T Troubleshoot & Resolve Tool's icons with, however, no "Exit" option. You could choose Wi-Fi options should you need them, but you could not stop the program with force after a reboot as they are not in the Processes or the Services Tables. Maybe the best way was to prevent them from starting at all at boot time. The "Control Panel" in Microsoft Windows Vista has the option sequence: Control Panel > Programs > Default Programs > Stop a program from running at startup . Clicking on this sequence resulted in a most surprising display stating that the "Windows Defender" was not running: And, clicking on the "Turn on and open Windows Defender", resulted in a no so surprising display: as I use the current and recommended Microsoft Security Essentials instead of the obsolete "Windows Defender". This is a bug in the most recent Microsoft Windows Vista Home Premium and I do not know its resolution yet. Once installed, AT&T Troubleshoot & Resolve Tool seems to be the source of the problem, should you have no problems with the network. Should you have problems with the network, however, it would have helped you to resolve them. Amazing... I decided to completely uninstall this Tool. It did uninstall taking all of the AT&T "Globe" icons with it, leaving other AT&T service programs functional, but with standard file icons. I found the icon in the harmless downloader for the Tool, and linked those icons to it, saving the "Globe". There remains the problem of startup, should one have trouble with the network in the future as one would need the network now to get the Tool. The answer, as always, is simple: Use the CD that came with the modem that has an earlier version of the Tool, and "use its update option to get the new version", should you need it. Should that not work, keep calm and read this message again from the start. The network excessive load pulse problem was gone now and it was 1 AM today, when I decided to type this message to the Tech Forum. I had started around 10 AM yesterday. I went to the Microsoft web page, and after requesting a password reset, I logged in. They had reorganized the Web page and I could not find the Tech Forums. I decided to wait until morning and went to sleep. Around noon, I located the Tech Forums with a global search and typed the message in. My next reply does have the Task Manager CPU Load Display with the network connected after the AT&T Troubleshoot & Resolve Tool is uninstalled. I could not enter that one into this message due to the "two pictures per message" limit. You can compare it with the ones in my December 3, 2011 original message and the following ones. -- Yekta PS: If you need a Flight Instructor in the Los Angeles area, do not hesitate to let me know...
Free Windows Admin Tool Kit Click here and download it now
November 15th, 2012 5:43pm

I graduated to become a Certified Flight Instructor ASE, AME, IA on September 24, 2012. I finally had some time to resolve the original problem I had run into, as illustrated in my starting message dated December 3, 2011 above. In the mean time, my network supplier AT and T had raised the cost of the network connection to nearly twice what it was before as their initial two year offer had ran through its course. I chose the lower speed option to hold the cost about the same as it was before. With the lower speed network, the load on the CPU stayed the same, going up to 100 percent in pulses as I had shown before. This was utterly ridiculous. I know, in detail, that the hardware is built in such a way not to exhibit any such behavior. The Microsoft Windows Vista Home Premium, as I had shown above, was not the cause of this behavior either. Yesterday, the regular Microsoft Windows Update notice came in with their latest bug fixes to the operating system. The network load took much longer time than expected due to the pulsing behavior. I decided to fix this problem once and for all, right there. The network interface chip on the motherboard of this computer is a Realtek RTL 8139. I have used this chip in many different places under many different configurations and under different operating systems for about than 10 years. It is a very fine chip that works very well. I also know that the motherboard architecture is also arranged correctly to accommodate this chip. To make sure that there is nothing broken in the motherboard LAN interface, I shut the on board LAN adapter chip down in the BIOS set up, installed a Realtek RTL 8169 PCI Gigabit LAN adapter in the one unused PCI slot in the computer, and booted the computer back up. The Microsoft Windows Vista recognized the new card and installed the driver for it. It also offered an update to the new driver. I installed the new update, and then rebooted the computer again. The network connected through the DSL modem as it did before, with exactly the same pulsing behavior. So, the hardware, as I had predicted, was never at fault. I left the new card in place, as it had the faster and better chip for future use on it. At this time, some part of some software in the computer, addressing the network interface was almost surely causing the problem. Almost surely, as the problem could be caused by another remote system somehow addressing the DSL modem externally, as I had indicated in my previous messages. I decided to use the AT&T Troubleshoot & Resolve Tool, initially supplied on a CD ROM when I bought my DSL modem from AT&T, and later updated regularly through its own update option from the AT&T Web server. The tool (Version 2011) came up and went through its usual steps as I had shown in my previous messages. It showed nothing different than I had encountered before. I decided to go through all of its options to make sure nothing else had changed in its "world" of software. Everything worked until I asked it to check the computer system and the e-mail settings. Before it checked those, it checked with AT&T Web Server to see whether there was an update to itself. It found a new version (AT&T Troubleshoot & Resolve Tool Version 2012) of itself and proceeded to install it. It went through 99 percent of the installation and it got stuck at the end of it for about 40 minutes. It then came back with an error message that the installation stream was interrupted due to erroneous remote server behavior, and asked me to contact AT&T. I contacted the AT&T service through their Web chat option. I filled the Web chat form with the detailed description of the problem. An operator connected and after verifying account information, asked me whether my e-mail and network connections were working well. They were working well, and I told her so. She told me then to ignore the AT&T Troubleshoot & Resolve Tool message. I told her that that would be easy, but how could I then get the updates to the AT&T Troubleshoot & Resolve Tool as the update procedure crashed with the same message every time? She finally saw what I was getting at, and suggested that I read an online article about updating the Tool and that I could download the AT&T Troubleshoot & Resolve Tool separately from their Web server. She typed in a live link to the article, and we disconnected after I told her that I did not need anything else. The live link however, sent me to a web page "article not found" error, and then directed me to a questionnaire. I skipped the questionnaire about the service at this time, and "saved" the printed chat dialogue using the "chat" Tool's "Save" option. It printed a message stating that the typed contents were copied to the clipboard and I could then paste the clipboard contents anywhere I wanted. I exited the chat tool, opened the "Notepad" and tried to paste, only to find that nothing was in the clipboard. Well, I was still determined to solve the original problem. Undaunted, I went to the AT&T Web server and after a short search located a downloadable version of the AT&T Troubleshoot & Resolve Tool Version 2012 for DSL. It downloaded a small downloader for the real Tool. At this point, not wanting to miss even a transient event, I opened the Microsoft Windows Vista Task Manager, and set it to "Performance" display. I then ran the small downloader for the Tool on my machine. It came up with a small display advising me to wait and the Task manager CPU display showing the huge network pulses normally got even busier. The downloader checked the accounting details, machine suitability, and the proceeded to look for a previous version of the Tool before it updated it. It surely did find the AT&T Troubleshoot & Resolve Tool Version 2011 on the machine. It then advised me to use the "Update" command in that existing version 2011 of the AT&T Troubleshoot & Resolve Tool on the machine to accomplish the update. The only other option it offered was the "Exit" button from the downloader for the new version. At this point, probably anyone else in my position at the keyboard would have "detonated" was my feeling, but I was used to encountering complete non-working cycles like this. I chose the only way out of the downloader by mouse-clicking the "Exit" button and I noted that the downloader did something entirely unexpected, on the Task Manager Performance CPU display: It somehow shut the huge network pulses down completely. With the network connected, and e-mail and web access completely working, there were no more large network related load pulses. I concluded that all previous versions of the AT&T Troubleshoot & Resolve Tool were the cause of those network related load pulses, although none of their processes appear in the Task Manager Processes or Services Tables. Presently, with all of its previous versions buggy in the way described above and the its update loop completely useless, the AT&T Troubleshoot & Resolve Tool Version 2011 somehow pointed to itself as the culprit in a most indirect way. I decided to uninstall it. It did uninstall using its Uninstall utility in the Programs Section of the Control Panel. I verified that the network load pulses no longer appeared even after a complete shutdown and reboot, as long as the AT&T Troubleshoot & Resolve Tool Version 2011 was not installed into the system. Now, I had to get the AT&T Troubleshoot & Resolve Tool Version 2012 into the system. I again downloaded the downloader for it making sure that none of those odd network related load pulses appear again. I ran it again, and after going through the steps mentioned above, it asked for AT&T network membership password, and then proceeded to install the Version 2012 one piece at a time through the network. It took a long time to do this, but it managed to completely install it. And, after a reboot, it did what I exactly did not want it to do: It brought the network related load pulses back. The culprit was now totally identified. The AT&T Troubleshoot & Resolve Tool was somehow always running continuously when I did not want it to run at all. I noted the two small AT&T icons on the right side of the standard bottom taskbar, and sure enough they were the AT&T Troubleshoot & Resolve Tool's icons with, however, no "Exit" option. You could choose Wi-Fi options should you need them, but you could not stop the program with force after a reboot as they are not in the Processes or the Services Tables. Maybe the best way was to prevent them from starting at all at boot time. The "Control Panel" in Microsoft Windows Vista has the option sequence: Control Panel > Programs > Default Programs > Stop a program from running at startup . Clicking on this sequence resulted in a most surprising display stating that the "Windows Defender" was not running: And, clicking on the "Turn on and open Windows Defender", resulted in a no so surprising display: as I use the current and recommended Microsoft Security Essentials instead of the obsolete "Windows Defender". This is a bug in the most recent Microsoft Windows Vista Home Premium and I do not know its resolution yet. Once installed, AT&T Troubleshoot & Resolve Tool seems to be the source of the problem, should you have no problems with the network. Should you have problems with the network, however, it would have helped you to resolve them. Amazing... I decided to completely uninstall this Tool. It did uninstall taking all of the AT&T "Globe" icons with it, leaving other AT&T service programs functional, but with standard file icons. I found the icon in the harmless downloader for the Tool, and linked those icons to it, saving the "Globe". There remains the problem of startup, should one have trouble with the network in the future as one would need the network now to get the Tool. The answer, as always, is simple: Use the CD that came with the modem that has an earlier version of the Tool, and "use its update option to get the new version", should you need it. Should that not work, keep calm and read this message again from the start. The network excessive load pulse problem was gone now and it was 1 AM today, when I decided to type this message to the Tech Forum. I had started around 10 AM yesterday. I went to the Microsoft web page, and after requesting a password reset, I logged in. They had reorganized the Web page and I could not find the Tech Forums. I decided to wait until morning and went to sleep. Around noon, I located the Tech Forums with a global search and typed the message in. My next reply does have the Task Manager CPU Load Display with the network connected after the AT&T Troubleshoot & Resolve Tool is uninstalled. I could not enter that one into this message due to the "two pictures per message" limit. You can compare it with the ones in my December 3, 2011 original message and the following ones. -- Yekta PS: If you need a Flight Instructor in the Los Angeles area, do not hesitate to let me know...
November 15th, 2012 5:43pm

I graduated to become a Certified Flight Instructor ASE, AME, IA on September 24, 2012. I finally had some time to resolve the original problem I had run into, as illustrated in my starting message dated December 3, 2011 above. In the mean time, my network supplier AT and T had raised the cost of the network connection to nearly twice what it was before as their initial two year offer had ran through its course. I chose the lower speed option to hold the cost about the same as it was before. With the lower speed network, the load on the CPU stayed the same, going up to 100 percent in pulses as I had shown before. This was utterly ridiculous. I know, in detail, that the hardware is built in such a way not to exhibit any such behavior. The Microsoft Windows Vista Home Premium, as I had shown above, was not the cause of this behavior either. Yesterday, the regular Microsoft Windows Update notice came in with their latest bug fixes to the operating system. The network load took much longer time than expected due to the pulsing behavior. I decided to fix this problem once and for all, right there. The network interface chip on the motherboard of this computer is a Realtek RTL 8139. I have used this chip in many different places under many different configurations and under different operating systems for about than 10 years. It is a very fine chip that works very well. I also know that the motherboard architecture is also arranged correctly to accommodate this chip. To make sure that there is nothing broken in the motherboard LAN interface, I shut the on board LAN adapter chip down in the BIOS set up, installed a Realtek RTL 8169 PCI Gigabit LAN adapter in the one unused PCI slot in the computer, and booted the computer back up. The Microsoft Windows Vista recognized the new card and installed the driver for it. It also offered an update to the new driver. I installed the new update, and then rebooted the computer again. The network connected through the DSL modem as it did before, with exactly the same pulsing behavior. So, the hardware, as I had predicted, was never at fault. I left the new card in place, as it had the faster and better chip for future use on it. At this time, some part of some software in the computer, addressing the network interface was almost surely causing the problem. Almost surely, as the problem could be caused by another remote system somehow addressing the DSL modem externally, as I had indicated in my previous messages. I decided to use the AT&T Troubleshoot & Resolve Tool, initially supplied on a CD ROM when I bought my DSL modem from AT&T, and later updated regularly through its own update option from the AT&T Web server. The tool (Version 2011) came up and went through its usual steps as I had shown in my previous messages. It showed nothing different than I had encountered before. I decided to go through all of its options to make sure nothing else had changed in its "world" of software. Everything worked until I asked it to check the computer system and the e-mail settings. Before it checked those, it checked with AT&T Web Server to see whether there was an update to itself. It found a new version (AT&T Troubleshoot & Resolve Tool Version 2012) of itself and proceeded to install it. It went through 99 percent of the installation and it got stuck at the end of it for about 40 minutes. It then came back with an error message that the installation stream was interrupted due to erroneous remote server behavior, and asked me to contact AT&T. I contacted the AT&T service through their Web chat option. I filled the Web chat form with the detailed description of the problem. An operator connected and after verifying account information, asked me whether my e-mail and network connections were working well. They were working well, and I told her so. She told me then to ignore the AT&T Troubleshoot & Resolve Tool message. I told her that that would be easy, but how could I then get the updates to the AT&T Troubleshoot & Resolve Tool as the update procedure crashed with the same message every time? She finally saw what I was getting at, and suggested that I read an online article about updating the Tool and that I could download the AT&T Troubleshoot & Resolve Tool separately from their Web server. She typed in a live link to the article, and we disconnected after I told her that I did not need anything else. The live link however, sent me to a web page "article not found" error, and then directed me to a questionnaire. I skipped the questionnaire about the service at this time, and "saved" the printed chat dialogue using the "chat" Tool's "Save" option. It printed a message stating that the typed contents were copied to the clipboard and I could then paste the clipboard contents anywhere I wanted. I exited the chat tool, opened the "Notepad" and tried to paste, only to find that nothing was in the clipboard. Well, I was still determined to solve the original problem. Undaunted, I went to the AT&T Web server and after a short search located a downloadable version of the AT&T Troubleshoot & Resolve Tool Version 2012 for DSL. It downloaded a small downloader for the real Tool. At this point, not wanting to miss even a transient event, I opened the Microsoft Windows Vista Task Manager, and set it to "Performance" display. I then ran the small downloader for the Tool on my machine. It came up with a small display advising me to wait and the Task manager CPU display showing the huge network pulses normally got even busier. The downloader checked the accounting details, machine suitability, and the proceeded to look for a previous version of the Tool before it updated it. It surely did find the AT&T Troubleshoot & Resolve Tool Version 2011 on the machine. It then advised me to use the "Update" command in that existing version 2011 of the AT&T Troubleshoot & Resolve Tool on the machine to accomplish the update. The only other option it offered was the "Exit" button from the downloader for the new version. At this point, probably anyone else in my position at the keyboard would have "detonated" was my feeling, but I was used to encountering complete non-working cycles like this. I chose the only way out of the downloader by mouse-clicking the "Exit" button and I noted that the downloader did something entirely unexpected, on the Task Manager Performance CPU display: It somehow shut the huge network pulses down completely. With the network connected, and e-mail and web access completely working, there were no more large network related load pulses. I concluded that all previous versions of the AT&T Troubleshoot & Resolve Tool were the cause of those network related load pulses, although none of their processes appear in the Task Manager Processes or Services Tables. Presently, with all of its previous versions buggy in the way described above and the its update loop completely useless, the AT&T Troubleshoot & Resolve Tool Version 2011 somehow pointed to itself as the culprit in a most indirect way. I decided to uninstall it. It did uninstall using its Uninstall utility in the Programs Section of the Control Panel. I verified that the network load pulses no longer appeared even after a complete shutdown and reboot, as long as the AT&T Troubleshoot & Resolve Tool Version 2011 was not installed into the system. Now, I had to get the AT&T Troubleshoot & Resolve Tool Version 2012 into the system. I again downloaded the downloader for it making sure that none of those odd network related load pulses appear again. I ran it again, and after going through the steps mentioned above, it asked for AT&T network membership password, and then proceeded to install the Version 2012 one piece at a time through the network. It took a long time to do this, but it managed to completely install it. And, after a reboot, it did what I exactly did not want it to do: It brought the network related load pulses back. The culprit was now totally identified. The AT&T Troubleshoot & Resolve Tool was somehow always running continuously when I did not want it to run at all. I noted the two small AT&T icons on the right side of the standard bottom taskbar, and sure enough they were the AT&T Troubleshoot & Resolve Tool's icons with, however, no "Exit" option. You could choose Wi-Fi options should you need them, but you could not stop the program with force after a reboot as they are not in the Processes or the Services Tables. Maybe the best way was to prevent them from starting at all at boot time. The "Control Panel" in Microsoft Windows Vista has the option sequence: Control Panel > Programs > Default Programs > Stop a program from running at startup . Clicking on this sequence resulted in a most surprising display stating that the "Windows Defender" was not running: And, clicking on the "Turn on and open Windows Defender", resulted in a no so surprising display: as I use the current and recommended Microsoft Security Essentials instead of the obsolete "Windows Defender". This is a bug in the most recent Microsoft Windows Vista Home Premium and I do not know its resolution yet. Once installed, AT&T Troubleshoot & Resolve Tool seems to be the source of the problem, should you have no problems with the network. Should you have problems with the network, however, it would have helped you to resolve them. Amazing... I decided to completely uninstall this Tool. It did uninstall taking all of the AT&T "Globe" icons with it, leaving other AT&T service programs functional, but with standard file icons. I found the icon in the harmless downloader for the Tool, and linked those icons to it, saving the "Globe". There remains the problem of startup, should one have trouble with the network in the future as one would need the network now to get the Tool. The answer, as always, is simple: Use the CD that came with the modem that has an earlier version of the Tool, and "use its update option to get the new version", should you need it. Should that not work, keep calm and read this message again from the start. The network excessive load pulse problem was gone now and it was 1 AM today, when I decided to type this message to the Tech Forum. I had started around 10 AM yesterday. I went to the Microsoft web page, and after requesting a password reset, I logged in. They had reorganized the Web page and I could not find the Tech Forums. I decided to wait until morning and went to sleep. Around noon, I located the Tech Forums with a global search and typed the message in. My next reply does have the Task Manager CPU Load Display with the network connected after the AT&T Troubleshoot & Resolve Tool is uninstalled. I could not enter that one into this message due to the "two pictures per message" limit. You can compare it with the ones in my December 3, 2011 original message and the following ones. -- Yekta PS: If you need a Flight Instructor in the Los Angeles area, do not hesitate to let me know...
Free Windows Admin Tool Kit Click here and download it now
November 15th, 2012 5:43pm

Here is the Microsoft Windows Vista Home Premium Task Manager Performance Display after the removal of the AT&T Troubleshoot & Resolve Tool: -The problem is obviously gone. -- Yekta
November 15th, 2012 5:48pm

Here is the Microsoft Windows Vista Home Premium Task Manager Performance Display after the removal of the AT&T Troubleshoot & Resolve Tool: -The problem is obviously gone. -- Yekta
Free Windows Admin Tool Kit Click here and download it now
November 15th, 2012 5:48pm

Here are some speed benchmarks after the network load pulse problem has been eliminated. The following Task Manager Performance display shows the load on the CPU of the computer with network on, with a network file transfer active (a 4.2 GB ISO DVD image is being downloaded), and with computer displaying live TV reception (30 frames per second) at the resolution of 1280x1024, from KDOC-DT 56.3 METV Los Angeles, from an external USB ATSC TV tuner, all at the same time. The show on the TV was a "Hogan's Heroes" episode with General Burkhalter's niece getting married. This was a normal color contrast and detail show at the ordinary NTSC resolution. The steady load on the CPU is around 75 percent. This was impossible to accomplish with the network load pulse problem present. The next Task Manager Performance display shows the load on the CPU of the computer with network on, with a network file transfer active (a 4.2 GB ISO DVD image is being downloaded), and with computer displaying live TV reception (30 frames per second) at the resolution of 1280x1024, from KDOC-DT 56.3 METV Los Angeles, from an external USB ATSC TV tuner, again all at the same time. The show on the TV was a "Batman" episode with Shame, Calamity Jan, and Frontier Fanny together with henchmen Chief Standing Pat and F.R.E.D against Batman, Robin and Batgirl in the Great Train Robbery. This was a very high color contrast and detail show at the ordinary NTSC resolution. The steady load on the CPU is still around 75 percent. This again was impossible to accomplish with the network load pulse problem present. My next reply shows what happens when a HD-TV station received. -- Yekta
November 18th, 2012 1:48am

Here are some speed benchmarks after the network load pulse problem has been eliminated. The following Task Manager Performance display shows the load on the CPU of the computer with network on, with a network file transfer active (a 4.2 GB ISO DVD image is being downloaded), and with computer displaying live TV reception (30 frames per second) at the resolution of 1280x1024, from KDOC-DT 56.3 METV Los Angeles, from an external USB ATSC TV tuner, all at the same time. The show on the TV was a "Hogan's Heroes" episode with General Burkhalter's niece getting married. This was a normal color contrast and detail show at the ordinary NTSC resolution. The steady load on the CPU is around 75 percent. This was impossible to accomplish with the network load pulse problem present. The next Task Manager Performance display shows the load on the CPU of the computer with network on, with a network file transfer active (a 4.2 GB ISO DVD image is being downloaded), and with computer displaying live TV reception (30 frames per second) at the resolution of 1280x1024, from KDOC-DT 56.3 METV Los Angeles, from an external USB ATSC TV tuner, again all at the same time. The show on the TV was a "Batman" episode with Shame, Calamity Jan, and Frontier Fanny together with henchmen Chief Standing Pat and F.R.E.D against Batman, Robin and Batgirl in the Great Train Robbery. This was a very high color contrast and detail show at the ordinary NTSC resolution. The steady load on the CPU is still around 75 percent. This again was impossible to accomplish with the network load pulse problem present. My next reply shows what happens when a HD-TV station received. -- Yekta
Free Windows Admin Tool Kit Click here and download it now
November 18th, 2012 1:48am

Here are some speed benchmarks after the network load pulse problem has been eliminated. The following Task Manager Performance display shows the load on the CPU of the computer with network on, with a network file transfer active (a 4.2 GB ISO DVD image is being downloaded), and with computer displaying live TV reception (30 frames per second) at the resolution of 1280x1024, from KDOC-DT 56.3 METV Los Angeles, from an external USB ATSC TV tuner, all at the same time. The show on the TV was a "Hogan's Heroes" episode with General Burkhalter's niece getting married. This was a normal color contrast and detail show at the ordinary NTSC resolution. The steady load on the CPU is around 75 percent. This was impossible to accomplish with the network load pulse problem present. The next Task Manager Performance display shows the load on the CPU of the computer with network on, with a network file transfer active (a 4.2 GB ISO DVD image is being downloaded), and with computer displaying live TV reception (30 frames per second) at the resolution of 1280x1024, from KDOC-DT 56.3 METV Los Angeles, from an external USB ATSC TV tuner, again all at the same time. The show on the TV was a "Batman" episode with Shame, Calamity Jan, and Frontier Fanny together with henchmen Chief Standing Pat and F.R.E.D against Batman, Robin and Batgirl in the Great Train Robbery. This was a very high color contrast and detail show at the ordinary NTSC resolution. The steady load on the CPU is still around 75 percent. This again was impossible to accomplish with the network load pulse problem present. My next reply shows what happens when a HD-TV station received. -- Yekta
November 18th, 2012 1:48am

And, here is the Task Manager Performance with network on, with a network file transfer active (a 4.2 GB ISO DVD image is being downloaded), and with computer displaying live TV reception (about 10+ frames per second, occasionally faster) at the resolution of 1280x1024 (dark edge around for16x9 aspect ratio), from KTLA-DT Channel 5 Los Angeles, from an external USB ATSC TV tuner, again all at the same time. The show on the TV was "KTLA News At 10, 11/17/2012. This was an HD-TV broadcast at the HD-TV resolution. The steady load on the CPU was just under 100 percent and the computer worked without ever locking up. This again was impossible to accomplish with the network load pulse problem present. -- Yekta
Free Windows Admin Tool Kit Click here and download it now
November 18th, 2012 2:25am

And, here is the Task Manager Performance with network on, with a network file transfer active (a 4.2 GB ISO DVD image is being downloaded), and with computer displaying live TV reception (about 10+ frames per second, occasionally faster) at the resolution of 1280x1024 (dark edge around for16x9 aspect ratio), from KTLA-DT Channel 5 Los Angeles, from an external USB ATSC TV tuner, again all at the same time. The show on the TV was "KTLA News At 10, 11/17/2012. This was an HD-TV broadcast at the HD-TV resolution. The steady load on the CPU was just under 100 percent and the computer worked without ever locking up. This again was impossible to accomplish with the network load pulse problem present. -- Yekta
November 18th, 2012 2:25am

And, here is the Task Manager Performance with network on, with a network file transfer active (a 4.2 GB ISO DVD image is being downloaded), and with computer displaying live TV reception (about 10+ frames per second, occasionally faster) at the resolution of 1280x1024 (dark edge around for16x9 aspect ratio), from KTLA-DT Channel 5 Los Angeles, from an external USB ATSC TV tuner, again all at the same time. The show on the TV was "KTLA News At 10, 11/17/2012. This was an HD-TV broadcast at the HD-TV resolution. The steady load on the CPU was just under 100 percent and the computer worked without ever locking up. This again was impossible to accomplish with the network load pulse problem present. -- Yekta
Free Windows Admin Tool Kit Click here and download it now
November 18th, 2012 2:25am

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

Other recent topics Other recent topics