I had to install it on the affected computer and run it with promiscuous mode disabled. I could not catch this traffic between both computers from mine using Wireshark. Removing the old printer from Windows XP and its associated TCP/IP Printer Port solved the problem. Implementation that must send WoL from different network do this by placing a WoL server on the LAN, and send. Broadcasts do not cross routers because this is a huge security hole. To do that, you must send the IP packet to either the network or limited broadcast address. There were still documents in the printing queue, so the Windows XP computer was continuously sending TCP SYN packets to the Windows 7 computer, thinking it was the network printer. WoL frames are sent to the broadcast MAC address, ffff:ffff:ffff. This computer still had the old network printer configured, pointing to the local IP address that now belongs to the Windows 7 computer having the problems. The computer sending the packets is old, and it is always on as it is used sometimes to run software that only works in Windows XP. The IP of the Windows 7 computer belonged before to a long-time discarded HP printer. The Windows 7 computer was continuously receiving TCP SYN packets to the 9100 port from another computer in the same LAN, waking up as a result when "Wake on Pattern Match" was activated. I am going to check if this computer is receiving any of these. The other PCs have this option enable too, but they do not randomly wake up. According to the default patterns are: magic packet, NetBIOS name query, TCPv4 SYN, TCPv6 SYN, IPv6 Neighbour Solicitation. This "Wake on Pattern Match" option is enabled on the computer. I don't see anything weird when capturing all traffic to and from this computer either. But when I manually send WOL packets from different computers on the network Wireshark does catch these packets. I am sniffing the whole LAN with Wireshark using the capture filter "ether proto 0x0842 or udp", as suggested in and it does not detect anything. The thing is I cannot find who is sending WOL packets. Wake on Magic Packet Wake on Pattern Match After a bit of research, I found this Microsoft Technet article which defines the feature as follows: Defines if a network adapter is enabled to wake a computer on the magic packet. Also, although the BIOS does not have an specific option to disable WOL, it has a power saving option that switches off the network card when the computer is not running, and this solves the problem too. 161 My wireless adapter (Intel Dual Band Wireless-N 7260) has two settings in Device Manager which I cannot explain. I suspected it was a Wake-on-LAN issue since the beginning, and it looks like it: the problem disappears if the ethernet cable is disconnected before turning the computer off. There is a desktop computer in our LAN that keeps booting almost every time seconds after it has been turned off manually.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |