Cant connect to computers

Discussion in 'Server Networking' started by Dominick, Aug 21, 2006.

  1. Dominick

    Dominick Guest

    Im on a 2003 domain with xp clients and i am not able to connect to some pc's
    via Network neighborhood or just \\computername, i get the "\\computer name
    not accessible. might not have permissions blah, blah blah. The network path
    was not found. With 90% of the othere computer i can access just fine. I can
    ping computer name and ip just fine.

    i already disabled the simple file sharing, and disabled the firewall and
    unjoined domain, deleted pc and rejoined and still cant access the computer.

    Any suggestions would be appreciated.
    Dominick, Aug 21, 2006
    1. Advertisements

  2. What's the common factor between all the computers that you can't connect

    Are all the computers on the same subnet?

    Oliver O'Boyle, Aug 21, 2006
    1. Advertisements

  3. Dominick

    Dominick Guest

    Common factor, they are laptops. Some Sony some Dell. Joined to the domain
    within the past month or so.
    Dominick, Aug 21, 2006
  4. Common factor, they are laptops. Some Sony some Dell. Joined to the domain
    Network Neighbourhood relies on the Computer Browser service to display
    NetBIOS computer names. The Computer Broswer service can take upwards of 15
    minutes to identify new names.

    How much time elapses between when the laptops are placed on the network,
    and when you search for their names? Do the laptops EVER show up?

    Also, make sure they aren't configured to disable NetBIOS. This can be done
    manually, or via DHCP. Go to the WINS tab in the Local Area Connection

    Also, if the laptops are connected wirelessly, make sure you don't have any
    filters or firewall (local or on the AP/Router) that are blocking NetBIOS

    Oliver O'Boyle, Aug 21, 2006
  5. Dominick

    Dominick Guest

    I can see then in network neighborhood, just once i click them to access them
    i get the error. I enebled netbios on the laptop this morning and still the
    same. They are wired not wireless.
    Dominick, Aug 21, 2006
  6. I can see then in network neighborhood, just once i click them to access
    Do you get an error message, or timout message of some sort?

    If you don't get one via Network N., open a command prompt and type:

    net use x: \\computernam\c$

    use an administrator username and password, if prompted. What error do you
    get, if any?

    Oliver O'Boyle, Aug 22, 2006
  7. Dominick

    Dominick Guest

    I get "the network path could not be found" when doing net use x:
    Dominick, Aug 22, 2006
  8. Dominick

    Dominick Guest

    And just realized, from the DC i can access \\computer\c$
    Dominick, Aug 22, 2006
  9. Dominick

    a-pabore Guest


    I've seen this sometimes because of Winsock corruption. You can do the

    To resolve this issue, follow these steps.

    Warning Serious problems might occur if you modify the registry incorrectly
    by using Registry Editor or by using another method. These problems might
    require that you reinstall your operating system. Microsoft cannot guarantee
    that these problems can be solved. Modify the registry at your own risk.

    1. On a good known working XP client Click Start, and then click Run.
    2. In the Open box, type Regedit, and then press ENTER.
    3. Navigate to the following registry key:
    4. On the Registry menu, click Export Registry File.
    5. In the File name box, type the name of winsock and save to your desktop.
    6. Repeat steps 3 through 5 for the following registry key:

    7. On the not working client Delete the following keys from the registry:



    8. Copy the saved registry keys from the desktop of the known working
    client to the desktop of the not working client and double-click each of them
    to re-install the winsock and winsock2 registry entries, then reboot.

    Hopefully this helps.
    a-pabore, Aug 22, 2006
  10. Dominick

    Dominick Guest

    Ok, its getting there. Now when in Network Neighborhood they still get access
    error. But i figured out that once i access the good machine from the bad
    machine via network neighborhood then the good machine can access to bad
    machine. Hope that didn't confuse you.
    Dominick, Aug 22, 2006
  11. Dominick

    a-pabore Guest


    Okay, on the bad machines, it sounds like there is some firewall or Norton
    product blocking these connections. Can you run msconfig and click the
    Services tab and check the hide all Microsoft services then disable all the
    other services temporarily and reboot, then try the connection again.

    This will eliminate some other product blocking this sharing capability.
    a-pabore, Aug 23, 2006
  12. Dominick

    Dominick Guest


    Thanks for a response.

    I had the windows firewall service disable for about a week. I did do you
    suggestion by uncheckin all the other services, including symantec AV, and
    VPN. Unfortunately it still does the same thing.

    Computer a = bad computer
    Computer b = good computer

    computer b see computer a in NN(network Neighborhood), computer b dbl clicks
    on computer a and gets access error.

    Computer a see computer b in NN, computer a dbl clicks on computer b and im

    Now that the connection has been made, computer b can now access computer a
    for a short perio of time.

    Not sure how this all relates, it may be a WINS/NETBIOS issue but i am at a
    loss here. Any more suggestions??

    Dominick, Aug 23, 2006
  13. can computer "B" always ping computer "A" by IP, or does this only work
    AFTER computer "A" communicates with computer "B", as you described above?

    if so, wait for the connectivity to drop again, then try pinging by FQDN
    (, using the same sequence. Does this work?

    Oliver O'Boyle, Aug 23, 2006
  14. Dominick

    Dominick Guest

    computer B has no problem ever pinging computer a, either by ip or computer
    name even if they wont connect.

    So i go to compter a, and ping computer b it works and i can connect. Wierd.

    Its like computer b cannot initiate the communication first.
    Dominick, Aug 23, 2006
  15. Are you using DNS, WINS, or both?

    Oliver O'Boyle, Aug 23, 2006
  16. Dominick

    Dominick Guest


    Dominick, Aug 23, 2006
  17. I'm making as assumption a bit quickly here, but I'm willing to bet it's
    related to WINS.

    First, I hate WINS and never ever use it. I haven't used it since W2K cam
    out... If you can (and there are very few reasons why you can't these days),
    just get rid of it. It's a piece of junk, and it always breaks.

    Second, let's try removing WINS from the picture temporarily. If you can,
    take a test laptop and assign it a static IP, then have the interface
    register the IP with the DNS server. DO NOT give it any WINS addresses.

    Test and let me know what happens.

    Oliver O'Boyle, Aug 23, 2006
  18. Dominick

    Dominick Guest

    so here is what i did, i stopped and disabled my wins service, and took it
    out of the dhcp scope option. I will let the machines refresh and see what
    happent tomorrow morning.

    Thanks again for you help.
    Dominick, Aug 23, 2006
  19. Dominick

    Dominick Guest

    Ok, so its been about 24 hours and same thing. Can ping from b but cant
    access a. Once a pings b, then b can access a. Any more suggestions??
    Dominick, Aug 24, 2006
  20. what is your network topology? Are all the computer on the same subnet or
    are they split up somehow? Do you use layer 2 or layer 3 switches? Where is
    the DC, in relation to all your computers (same subnet, different subnet)?

    Oliver O'Boyle, Aug 24, 2006
    1. Advertisements

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments (here). After that, you can post your question and our members will help you out.