Local network share detection shoddy, but actual connection is fine. Windows XP.

Posted on 2007-10-01
Last Modified: 2010-03-17
Ok I've got 3 computers all running a variant of Windows XP. 2 of them are desktops running XP Pro and the third is a tablet running Windows XP Tablet PC Edition which is more or less like XP Pro.

Anywho I just reinstalled XP Pro on one of the desktops and have done very little to it aside from installing drivers and whatnot. However I can't see computers on my network and the Discoverer doesn't seem to be picking up any local shares despite the fact that they are there and open. Now if I manually enter in \\compname1 or \\compname2 it works just fine, but it won't discover them automatically.

A couple things to note:

I have a separate XP install on another partition that works just fine and was installed not too long before this latest one. In other words there is very little difference between the two installs and that one detects local shares just fine.

Secondly, the only thing I can think of that happened differently in the install process of the two was that I opened up Internet Explorer to get a driver before I had installed the ethernet driver. This caused a little network connection wizard to pop up, but I promptly dismissed it after I realized what was going on, so I don't think it made any substantial modifications, but I did flip through the first screen or two so I thought it might be worth a mention.
Question by:soydeedo
    LVL 63

    Accepted Solution


    ipconfig /all from both  XP partitions from a DOS window.
    In addition, do a dump of the System info by using

    winmsd - export a full report to a text file and compare.

    Lots of good info there.

    I hope this helps !

    Author Comment

    Well unfortunately [shouldn't it be fortunately? =P] after installing Visual Studio and its accompanying updates the problem seemed to right itself. Not sure what was installed during this process and VS was never installed on the other partition so I'm really curious what caused this behavior, but I guess 'till next time, eh?

    Thanks for the response. =)

    Write Comment

    Please enter a first name

    Please enter a last name

    We will never share this with anyone.

    Featured Post

    IT, Stop Being Called Into Every Meeting

    Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

    Mapping Drives using Group policy preferences Are you still using old scripts to map your network drives if so this article will show you how to get away for old scripts and move toward Group Policy Preference for mapping them. First things f…
    Trying to figure out group policy inheritance and which settings apply where can be a chore.  Here's a very simple summary I've written which might help.  Keep in mind, this is just a high-level conceptual overview where I try to avoid getting bogge…
    This tutorial will walk an individual through the steps necessary to join and promote the first Windows Server 2012 domain controller into an Active Directory environment running on Windows Server 2008. Determine the location of the FSMO roles by lo…
    This tutorial will walk an individual through the process of transferring the five major, necessary Active Directory Roles, commonly referred to as the FSMO roles from a Windows Server 2008 domain controller to a Windows Server 2012 domain controlle…

    737 members asked questions and received personalized solutions in the past 7 days.

    Join the community of 500,000 technology professionals and ask your questions.

    Join & Ask a Question

    Need Help in Real-Time?

    Connect with top rated Experts

    15 Experts available now in Live!

    Get 1:1 Help Now