What is happening is that every (15) minutes, the "Microsoft Networking" software is creating DNS queries and/or WINS Syncronization traffic for the Network Neighborhood. On a LAN, traffic like this isn't too bad but on a Dial-on-demand WAN connection, it can become VERY expensive.
To solve these issues, you should:
"It works, but it's unacceptable if you configure the clients' DNS properties manually (using the network control panel). Adding the key suggested in the knowledge base will cause win95 to remove your DNS server setting the next time you add/delete/change anything in the network control panel. The netswitch utility (www.bysnet.com/netsw.html) is a very handy way to change network related registry settings, sometimes avoiding the need to reboot to apply the changes. There's another solution involving adding special LMHOSTS file entries, but I can't find my copy of the information anymore. The solution that works for me is to unbind "client for microsoft networks" and "file sharing" from tcp/ip, and use a different protocol (netbeui or ipx/spx) for filesharing between my home network machines.
Filterout IP packets with the source port of (137) and destination port of (53). (That's Netbios-ns trying to do a dns lookup.)