Many new ISDN
router users are discovering that when Microsoft Windows 95 and/or NT
workstations are connected to the LAN, their ISDN router either:
Never lets the ISDN line go down
The ISDN line comes up even when
no one is using the machine(s)!!
The user never notices that the
line is coming up and down all the time until they receive a very EXPENSIVE
ISDN bill!
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:
Either remove the MS
networking client or follow advice from the
Microsoft Knowledge Base Article - 137368 for Win95
But a user on comp.dcom.ISDN
news group said: "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.)