RE: RE: Winroute (was BT Anytime thingy)

["Mark Hetherington \(egroups\)" <mark.egroups@xxxxxxx>]

Obviously the general applications running are the first thing to check,
but
given the regularity, it could well be a simple peer to peer networking
packet which triggers the dial up for DNS.

Windows peer to peer networking does do regular network checks in order to
create a new master browser if the current one has gone offline. To fix
this, you could force the host PC to be the browser and disable browser
capabilities on the rest. This way they should always ask the host PC for
network information rather than searching for it and attempting to
"take
over" should the current master browser disappear. Static IPS and use
of the
Windows hosts file will also assist in the case of it being a simple p2p
network issue since the hosts file takes priority over DNS requests.

It is worth trying static ips (if you are not already) and the hosts file
just to eliminate local requests causing the dial up since then you know
that one or more machines are looking to resolve an external address.

Personally I just use ICS for sharing the Internet connection rather than a
third party app so have no experience in WinRoute specific issues, but the
Microsoft support site has a number of documents about problems with ICS
that may equally apply to WinRoute so might be worth a read.

Mark.

-----Original Message-----
From: Kevin Hawkins [mailto:lists@xxxxxxx]
Sent: 07 September 2001 00:59
To: ukha_d@xxxxxxx
Subject: RE: [ukha_d] RE: Winroute (was BT Anytime thingy)


You can turn an option on for logging DNS server messages in the
advanced window for the debug log and also log the tcp and udp packets
here - that might shed some light.
What OS are your running on, what networking protocols are running and
could there be any tcp applications running ? - obvious ones like Outlook
or
less obvious like MSN messenger or a dynamic dns client or windows critcal
update perhaps -  or is it definately an OS originated function ?