Re: Cant connect to computers

Dominick,

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

RESOLUTION
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:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock
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:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

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

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock

HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Winsock2

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.

--
Regards,

Patrick Boren


"Dominick" wrote:

And just realized, from the DC i can access \\computer\c$

"Dominick" wrote:

I get "the network path could not be found" when doing net use x:
\\computernam\c$.



"Oliver O'Boyle" wrote:

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.

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


"Oliver O'Boyle" wrote:

Common factor, they are laptops. Some Sony some Dell. Joined to the
domain
within the past month or so.

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
interface.

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
traffic.

Oliver


"Oliver O'Boyle" wrote:

"Dominick" <Dominick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:80983ED6-56BC-4A30-BA1D-5D28F6F55546@xxxxxxxxxxxxxxxx
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.

What's the common factor between all the computers that you can't
connect
to?

Are all the computers on the same subnet?

Thanks,
Oliver









.

Relevant Pages

  • Re: Cant connect to computers
    ... Now that the connection has been made, ... machine via network neighborhood then the good machine can ... by using Registry Editor or by using another method. ... How much time elapses between when the laptops ...
    (microsoft.public.windows.server.networking)
  • Re: Constant Registry Corruption
    ... Does anyone know why the registry keeps breaking? ... For example a program which can automatically fix the registry if it ... Removing some spyware can damage the Winsock stack and you may not be able to connect to the Internet. ...
    (microsoft.public.windowsxp.general)
  • Re: winsocks
    ... you probably have a damaged winsock2 key in the registry. ... Then expand Components / Network / click on Protocol - ... Step 1: Delete registry keys ... It is important to restart the computer after deleting the Winsock keys. ...
    (microsoft.public.windowsxp.network_web)
  • Re: TV Media Adware and Restore
    ... registry or on the filesystem. ... The Winsock XP fix didn't work. ... correspond to the adware, but now I don't. ... I am almost positive the worm came on my computer with the TV Media ...
    (microsoft.public.windowsxp.help_and_support)
  • Re: Windows Firewall wont load
    ... Trying to back up the registry with Winsock and TCP Repair Utility, ... X Error saving file ... > torgeir, Microsoft MVP Scripting and WMI, Porsgrunn Norway ...
    (microsoft.public.windowsxp.security_admin)
Loading