Jump to content


 


Register a free account to unlock additional features at BleepingComputer.com
Welcome to BleepingComputer, a free community where people like yourself come together to discuss and learn how to use their computers. Using the site is easy and fun. As a guest, you can browse and view the various discussions in the forums, but can not create a new topic or reply to an existing one unless you are logged in. Other benefits of registering an account are subscribing to topics and forums, creating a blog, and having no ads shown anywhere on the site.


Click here to Register a free account now! or read our Welcome Guide to learn how to use this site.

Photo

Strange LAN problem


  • Please log in to reply
3 replies to this topic

#1 joebanana

joebanana

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:08:36 AM

Posted 26 October 2010 - 02:15 PM

Hello,

I have a weird ongoing problem at home.

Router : Belkin N+ (http://www.belkin.com/IWCatProductPage.process?Product_Id=459640#)

Computers :
File Server running XP Pro, wired
Gateway laptop (7 Premium), wireless
Acer Revo 3610 (7 Starter), wired
Gateway all-in-one (7 Premium), wireless

Everything is connected through DHCP.

The issue is that if I try to browse my network, sometimes (often), I will not see the name of some of my machines (especially FILESERVER).
If I try to connect to FILESERVER, it will say it can't be found.
However, if I try to connect through its IP address, it works just fine.

Then a bit later, I will see the names just fine, then again later, I won't see some of them.

This is not related to the router as I had a D-Link before that had the exact same issue.

Any idea why this would happen on such a random basis?

I just find it annoying that I have to map my shares (for backups or for my music library for example) using the IP address instead of the machine name.

Thanks in advance!

JoeB

BC AdBot (Login to Remove)

 


#2 ThunderZ

ThunderZ

  • Deactivated
  • 4,454 posts
  • OFFLINE
  •  
  • Gender:Male
  • Local time:08:36 AM

Posted 26 October 2010 - 02:24 PM

The first and only thing that comes to my mind are the power settings for the NIC on the machines in question. Try checking each via Device Manager and make sure any power savings settings are disabled.

#3 thrillhouse

thrillhouse

  • Members
  • 1,040 posts
  • OFFLINE
  •  
  • Gender:Male
  • Location:Va
  • Local time:09:36 AM

Posted 26 October 2010 - 03:10 PM

also, try tcp settings on all machines with netbios over tcp

#4 joebanana

joebanana
  • Topic Starter

  • Members
  • 6 posts
  • OFFLINE
  •  
  • Local time:08:36 AM

Posted 08 November 2010 - 09:53 AM

also, try tcp settings on all machines with netbios over tcp


This is what solved the problem (at least for the past couple of weeks!)

Thanks!




0 user(s) are reading this topic

0 members, 0 guests, 0 anonymous users