by oj » Dec 23rd, '12, 17:38
Is the IP multicast perchance? (240.0.0.x or thereabouts?) If so, that's windows network resource discovery at work. The machines basically play "Marco-Polo" on the network, asking for any reply within a certain IP range where things like windows media center servers live.
The best thing to do is disable that discovery on the windows machine. It's not easy using the windows advanced firewall control. (too many details) Try a thuird party 'firewall' like zone alarm, which makes things more comprehensible.
If it's an IP in the range of the LAN, it's still probably some kind of service discovery. (eg printers) Check what port(s) it's calling on, to identify the service, then disable it on the windows machine.
The tool for this is wireshark. Install/run it (as root) and capture a minute or two of traffic, then look through for the IP/port combination (aka "socket") from the offending machine.