We help IT Professionals succeed at work.

We've partnered with Certified Experts, Carl Webster and Richard Faulkner, to bring you two Citrix podcasts. Learn about 2020 trends and get answers to your biggest Citrix questions!Listen Now

x

VPN/Firewall router and WINS on a Windows 2003 Server

Guy_Adams
Guy_Adams asked
on
Medium Priority
653 Views
Last Modified: 2008-01-09
Hi All,

I have a single NIC Windows 2003 Server and a Netgear FVS318v3 with the latest firmware.

Every 40 mins the server sends a multicast message (IGMP) out to find WINS partners to 224.0.0.22 then follows it up on UDP 42 to address 224.0.1.24

The router promtly replys to this message with a ICMP "Destination Unreachable" message which the server then promtly reports as an error:

Event Type:      Error
Event Source:      Wins
Event Category:      None
Event ID:      4204
Date:            06/04/2006
Time:            13:56:13
User:            N/A
Computer:      OURSERVER
Description:
WINS could not read from the User Datagram Protocol (UDP) socket.

I know this is programmed behaviour as the server is looking for WINS partners but is there anything I can do to prevent this. I have found a few guides on how t do this for Windows 2000 server but the registry keys are different for 2003.

Any help would be much appreciated.

Regards

Guy_Adams
Comment
Watch Question

Commented:
This message means that WINS was unable to receive a name packet. Stop the WINS service. Then double-click Network in the Control Panel. Under the Protocols tab, verify that the TCP/IP driver is installed and running. Restart WINS if necessary to correct the problem." We have seen reports on this problem even when the TCP/IP seems to be running fine.

also give the Local System account read rights to the following registry key:

HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\SecurePipeServers\winreg

Author

Commented:
Thank you for the response but I have already tried that.

Also %Systemroot%\System32\Wins has the correct permissions.

Any other ideas?

Regards

Guy_Adams

Author

Commented:
I've managed to trace the packets which cause the error, i just need to disable the behaviour either on the server or on the router.

Regards

Guy_Adams
Commented:
I have found that it is best not to set up WINS. it does not actually needs in Windows2003 this error causing because of router response, u either unintall the wins service if u dont really need it, or stop the router reply if u can or u can edit the registry and extend the time to attempt for discovery and safely ignore this error, because it does not effect on any thing in your network. more you can statically define a replication partner.

for registry settings check this
http://support.microsoft.com/?id=151761

Not the solution you were looking for? Getting a personalized solution is easy.

Ask the Experts

Author

Commented:
Thanks again f_umar,

I think to be honest I will end up leaving it as in less than 14 days we have a new remote DC being put in place at another office conncted via a WAN link.

I wonder if a static route for the multicast address sent over the VPN to the new DC would resolve the issue?

I have rewarded the points to you for a swift response.

Thank you

Regards

Guy_Adams
Access more of Experts Exchange with a free account
Thanks for using Experts Exchange.

Create a free account to continue.

Limited access with a free account allows you to:

  • View three pieces of content (articles, solutions, posts, and videos)
  • Ask the experts questions (counted toward content limit)
  • Customize your dashboard and profile

*This site is protected by reCAPTCHA and the Google Privacy Policy and Terms of Service apply.

OR

Please enter a first name

Please enter a last name

8+ characters (letters, numbers, and a symbol)

By clicking, you agree to the Terms of Use and Privacy Policy.