I think this is just the usual Windows TCP/IP networking BS. I have these kind of complaints ever since I switched from Win95 Netbui to WinNT TCP/IP. All the times I have tried to get things working better, the only thing I discovered is that mapping drives generally work better then browsing the network. I thought Vista was suppose to replace the whole TCP/IP stack and fix a lot of these problems.
At 11:54 AM 2/24/2008, you wrote:
I appreciate the advice. Here's what gets me - I'm fairly knowledgeable about this sort of stuff and I'm not doing anything extraordinary. I have 3 windows machines and a MacBook on a home LAN with my Airport Extreme handling the DHCP duties. And this problem was happening with both the Netgear and D-link devices I was using before, as well as back when I only had 2 Windows machines on the system, so I am fairly sure it isn't any of the networking gear. Am I missing something critical about configuration for Windows file sharing? All I want to be able to do is transfer files and share media back and forth. If I get rid of NetBIOS, I would go into the Network config and remove File and Print Sharing? I know back in the day you had multiple network protocols you could bind to various adapters, so you could do NetBUI or NetBIOS over TCP/IP. Here's what I have now: Client for Microsoft Networks File and Printer Sharing for Microsoft Networks QoS Packet Scheduler TCP/IP I have no idea what these three are, I think they installed with my Wi-fi card (they only exist on my one machine): Jumpstart Wireless Intermediate Driver Wireless Intermediate Driver Link-Layer Topology Discovery Responder Wait a minute, now that I think about it, I remember back in the day having the IPX/SPX/NetBIOS protocol - should I have that running or no? ----- Brian Weeden On Sun, Feb 24, 2008 at 11:50 AM, Ben Ruset <[EMAIL PROTECTED]> wrote: > Your Mac is doing it because you have Windows file sharing turned on. > If you're not sharing anything on the Mac to Windows clients then you > shouldn't need to have it turned on. > > One thing that you could do to get around the browser issues would be to > not rely on NetBIOS for name resolution. You could do this one of two ways: > > 1) Give all of your machines static IP's, and make entries for each of > them in each machine's hosts file. > > 2) Set up a local DNS server, and have your DHCP server send over the IP > and hostname info to the DNS server when they register a lease. This is > easy to do with Windows DNS/DHCP, slightly harder with Linux, and > probably impossible if you have your home router handling DHCP. > > You'd have this problem even if you had a Windows Home Server or *nix > box running. For whatever reason NetBIOS over TCP/IP is not working > right in your environment. You'd have the same sort of problems > connecting to a Microsoft or Samba SMB share. Using something besides > NetBIOS for name resolution should net you some performance benefits. > > > Brian Weeden wrote: > > I've posted here before about this problem and really haven't solved > > anything yet. For those that haven't heard my ranting before, the issue > > with the Windows on a peer-to-peer network and browsing. If you have a > > <snip> >
