Member Avatar for Dani

I found this in a few different places around the 'net - hopefully it's helpful:

Slow Network Access Not Always Due to Scheduled Tasks Check

If you have very slow access to your network computers through "My Network Places" and have already deleted the Registry entry calling for a check of Scheduled Tasks on the other network computers (documented elsewhere on this site) AND you have multiple network adaptors (i.e. a cable or DSL connection through one NIC and an internal network using a second NIC) check the following:

  • Right-click on "My Network Places", go to Properties.
  • Right-click on the NIC that your cable/DSL connects to, and choose Properties.
  • Select Internet Protocol (TCP/IP), and click on Properties.
  • Click on "Advanced", go to "WINS" tab, and chose Disable NetBios over TCP/IP.
  • When you are back at your Network Connections page, right-click on the Broadband selection.
  • Choose "Properties", click on the Networking tab.
  • Again, choose TCP/IP, Properties, Advanced, WINS, and select "disable NetBios over TCP/IP".
  • 2 Contributors
  • 1 Reply
  • 186 Views
  • 3 Years Discussion Span
  • Latest Post Latest Post by Z28James

Dani AI

Generated

Good pointer from — this is a classic multi‑NIC symptom rather than a Scheduled Tasks bug. On systems with both an Internet‑facing adapter and an internal LAN adapter, name‑resolution and browse traffic (NetBIOS/WINS broadcasts and queries) can go out the wrong interface and wait on network timeouts. That delay shows up as slow enumeration in "My Network Places" even when the scheduled‑tasks registry tweak has already been applied.

A few diagnostics that add clarity without redoing the steps already posted:

ipconfig /all
route print
nbtstat -n
nbtstat -a <remote-IP-or-name>
net view \\hostname

These reveal which adapter is answering name requests, whether NetBIOS is enabled per adapter, and whether routing/metrics favor the broadband NIC. Temporarily disabling the broadband adapter is a quick way to confirm the source of the slowdown.

Options to consider beyond simply disabling NetBIOS on the public interface: ensure the internal NIC has the preferred binding order or a lower interface metric, remove Client for Microsoft Networks / File and Printer Sharing from the Internet adapter, and configure WINS/DNS only on the LAN adapter. Each change should be tested and rolled back if legacy SMB/NetBIOS name resolution is needed.

Cautions: disabling NetBIOS will break legacy name‑based discovery and some older SMB services. In Active Directory environments DNS handles most name resolution, but legacy apps may still rely on NetBIOS. These suggestions are most applicable to Windows 2000/XP era stacks; modern Windows adds LLMNR/mDNS and network‑location controls that change the troubleshooting surface. Thanks to for the original tip and to for the nostalgic bump.

Member Avatar for Z28James

Haha this is funny.

I remember the 1st time i found this website I was looking for an answer to something on google and I just bumped into it again.

Be a part of the DaniWeb community

We're a friendly, industry-focused community of developers, IT pros, digital marketers, and technology enthusiasts meeting, networking, learning, and sharing knowledge.