udp packets necessary for wifi connection

RULE:'DNS': PERMIT: In UDP, 172.16.0.1:1900->Loc:1900, OWNER:
C:\WINSYS\SVCHOST.EXE
RULE:'DNS': PERMIT: In UDP, 172.16.0.1:1900->Loc:1900, OWNER:
C:\WINSYS\SVCHOST.EXE
RULE:'DNS': PERMIT: In UDP, 172.16.0.1:1900->Loc:1900, OWNER:
C:\WINSYS\SVCHOST.EXE
RULE:'DNS': PERMIT: In UDP, 172.16.0.186:54605->Loc:2223, OWNER: no owner
RULE:'DNS': PERMIT: In UDP, 172.16.0.186:54605->Loc:2223, OWNER: no owner


On a XP system, public access AP, I am receiving floods of these
incoming UDP packets. If I block port 1900, I lose my assigned IP and
cannot reconnect. On another system windows 98SE, if I block port 1900,
no problem, stay connected.

Anyone know what the purpose of these incoming UDP packets is? They are
being sent by the gateway/dns server..

In message <hbans2$h9i$(E-Mail Removed)> colorpurple <(E-Mail Removed)>
was claimed to have wrote:

>RULE:'DNS': PERMIT: In UDP, 172.16.0.1:1900->Loc:1900, OWNER:
>C:\WINSYS\SVCHOST.EXE
>RULE:'DNS': PERMIT: In UDP, 172.16.0.1:1900->Loc:1900, OWNER:
>C:\WINSYS\SVCHOST.EXE
>RULE:'DNS': PERMIT: In UDP, 172.16.0.1:1900->Loc:1900, OWNER:
>C:\WINSYS\SVCHOST.EXE
>RULE:'DNS': PERMIT: In UDP, 172.16.0.186:54605->Loc:2223, OWNER: no owner
>RULE:'DNS': PERMIT: In UDP, 172.16.0.186:54605->Loc:2223, OWNER: no owner
>
>
>On a XP system, public access AP, I am receiving floods of these
>incoming UDP packets. If I block port 1900, I lose my assigned IP and
>cannot reconnect. On another system windows 98SE, if I block port 1900,
>no problem, stay connected.
>
>Anyone know what the purpose of these incoming UDP packets is? They are
>being sent by the gateway/dns server..

Port 1900 is uPNP, it shouldn't be required in most cases unless you're
using uPNP, but I've seen weirder things.