In news:
[email protected],
I saw no indication in the OP that "Workgroups" was a component, or that it
"APPEARS" to be anything, but of course they stated nothing about the
network topology. The inability to sense the other computer may be a very
simple thing to solve, but blindly assuming complexities is a tertiary or
quaternary step after the fundamentals of "route print" and "ipconfig /all",
regardless of the so-called "99.9%" that you pulled out of a hat.
The secondary steps are of course to ping the other computer, the router,
the DNS servers and then perform an nslookup on e.g. google.com
Installing additional, obsolete 1980's software components complicates
things before the networking setup fundamentals and functionality are
understood.
The OP references My Network Places. This, to me, inferred that he
was using workgroups. If he/she was not, they would have likely said
as much. And in ALL the cases where workgroups appeared to be set up
correctly, using the quick and dirty fix of adding the NetBIOS
protocol ALWAYS made machines visible on the network to each other
when I have had to fix what others have broken in multiple attempts to
remedy machines not seeing each other in a workgroup (similar to how
the OP tried multiple times). All I know is it ALWAYS works. I have
tried, forensically, to analyze why a workgroup that appeared to be
set up properly doesn't work after it's been messed with too many
times. It has nothing to do with an 80's protocol. Maybe you've just
wiped someone's machine and started from scratch to fix a problem of
machines not seeing each other in a workgroup, I just add the protocol
and, from personal experience, know it always fixes the problem if
machines cannot see each other on the LAN. The users is obviously NOT
his own domain and does NOT need to NSLOOKUP anything. You obviously
did not read his post. He/she is a home user with a home network.
Ping, fine. Ping tells you if someone is live on the LAN and that's
it. The OP probably see's a vestige of the machine name visible in his
My Network Places and doesn't realize it's a broken pointer to one of
the seven attempts that was half successful at making the machine show
up in My Network Places. He needs to delete that pointer, and the
NWlink protocol, bounce both machines, and they WILL see each other on
next discovery. You gave the OP no solution, just some non-useful
troubleshooting tips. You've obviously never encountered this problem,
I have. I have fixed it every single time using the NWlink protocol. I
don't know how, nor do I care, I just know it works.
