Re: Cant connect to computers


"Dominick" <Dominick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:ACC37A5B-5E36-44D3-A473-C903590182BB@xxxxxxxxxxxxxxxx
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??


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

"Dominick" wrote:

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.

"Oliver O'Boyle" wrote:


"Dominick" <Dominick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:361658B3-850F-4556-9EE2-AFBECD4B1538@xxxxxxxxxxxxxxxx
Both


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

"Oliver O'Boyle" wrote:


"Dominick" <Dominick@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:320BC977-FB28-4F5A-8EB6-851B3A672AE7@xxxxxxxxxxxxxxxx
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.

Are you using DNS, WINS, or both?

Oliver


"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


.

Relevant Pages

  • Re: Old LAN Connection
    ... To rid your computer of the phantom adaptor follow the instructions here: http://support.microsoft.com/kb/269155 If after doing the above you still have problems then delete the registry entries for the network adapter. ... Remembering back to the original post, the problem is that although my network connection works fine for me to be on the Internet, I can never see the status. ... You could try deleting all the NIC devices shown in device manager, rebooting the PC, and letting XP find the NIC and reinstall the device drivers. ...
    (microsoft.public.windowsxp.general)
  • RE: 0x7c911e58 error
    ... was still using the registry during log off. ... Your computer was not assigned an address from the network (by the DHCP ... Server) for the Network Card with network address 000E3541722C. ...
    (microsoft.public.windowsxp.general)
  • Re: For the AdaOS folks
    ... > could be on any workstation in the network. ... >>root file system, which obviously is only local to one node. ... - Joining (hard pressed to think of any registry entry I wanted ...
    (comp.lang.ada)
  • Re: Cant connect to computers
    ... 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 ... How much time elapses between when the laptops are placed on ...
    (microsoft.public.windows.server.networking)
  • Re: WCESmgr ActiveSync app wont start
    ... when try to open ActiveSync WCESMGR will appear in running processes for a ... and the connection is available via Network Connections. ... What files were left in registry to delete and what program did you ...
    (microsoft.public.pocketpc.activesync)