Re: Cant connect to computers

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.

"Oliver O'Boyle" wrote:


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

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

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
(host.domain.com), using the same sequence. Does this work?

Oliver



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

Thanks,
Dominick

"a-pabore" wrote:

Dominick,

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.
--
Regards,

Patrick Boren


"Dominick" wrote:

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.



"a-pabore" wrote:

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 access ... Warning Serious problems might occur if you modify the registry ... How much time elapses between when the laptops are ...
    (microsoft.public.windows.server.networking)
  • Re: Cant connect to computers
    ... This will eliminate some other product blocking this sharing capability. ... machine via network neighborhood then the good machine can access to bad ... Warning Serious problems might occur if you modify the registry incorrectly ... Go to the WINS tab in the Local Area Connection ...
    (microsoft.public.windows.server.networking)
  • Re: Cant connect to computers
    ... computer b see computer a in NN(network Neighborhood), ... Now that the connection has been made, computer b can now access computer ... machine via network neighborhood then the good machine can access to ... Warning Serious problems might occur if you modify the registry ...
    (microsoft.public.windows.server.networking)
  • Re: Cant connect to computers
    ... "Oliver O'Boyle" wrote: ... then try the connection again. ... machine via network neighborhood then the good machine can access to ... Warning Serious problems might occur if you modify the registry ...
    (microsoft.public.windows.server.networking)
  • Re: Cant connect to computers
    ... Now when in Network Neighborhood they still get access ... Warning Serious problems might occur if you modify the registry incorrectly ... NetBIOS computer names. ... Do the laptops EVER show up? ...
    (microsoft.public.windows.server.networking)
Loading