Workgroup computer which is not running, does NOT disappear fromworkgroup

[kimiraikkonen]

Hi,
I have 2 workgroup computers on my LAN. Both of them can see
themselves fine, but the problem is different:

When "computer 2" computer leaves from LAN (shutdowns its Windows XP),
after "computer 2" shutdowns completely, i'm still able to see
"computer 2" from "computer 1" in "view workgroup computers" and using
"net view" command prompt. "Computer 2" never disappears from
workgroup eventhough it was shutdown until i reboot "computer 1".

Is it a bug in XP Pro SP2?

Thanks!

 

[Jack \(MVP-Networking\).]

Hi
That is OK it should be like this.
Jack (MVP-Networking).

 

[kimiraikkonen]

Hi
That is OK it should be like this.
Jack (MVP-Networking).

Thanks for informing.

 

[Jim]

Hi,
I have 2 workgroup computers on my LAN. Both of them can see
themselves fine, but the problem is different:

When "computer 2" computer leaves from LAN (shutdowns its Windows XP),
after "computer 2" shutdowns completely, i'm still able to see
"computer 2" from "computer 1" in "view workgroup computers" and using
"net view" command prompt. "Computer 2" never disappears from
workgroup eventhough it was shutdown until i reboot "computer 1".

Is it a bug in XP Pro SP2?

Thanks!

No. The only way that computer 1 would know that computer 2 has shutdown
occurs when
computer 1 tries to access computer 2. This is a consequence of the way
that the internet was
designed so many years ago.

Jim

 

[kimiraikkonen]

No. The only way that computer 1 would know that computer 2 has shutdown
occurs when
computer 1 tries to access computer 2. This is a consequence of the way
that the internet was
designed so many years ago.

Jim

But it's not normal in fact, Windows developers should have
implemented a function that queries computers availability eveytime.
Seeing a non-running computer on a workgroup(previously was on the
lAN) but not accessing it with a error may mean more than one thing.

If Windows queried or refreshed current "real" availabilty of
workgroup computers, we would easily be aware of status of computer 2
if it's really shutdown and left the LAN.

 

[Jack \(MVP-Networking\).]

Hi
Hi
Windows Client OS' are used for wide purposes (from the unknowledgeable
End-User to the Big corporate WANS), and are backward compatible to
accommodate previous systems.
Sometimes compromise are made to allow these accommodations.
However it is always easier to "badmouth" and complain then to join the
quest for innovation.
Jack (MVP-Networking).
P.S. This represent my personal feeling and has nothing to do wit any other
entity.

 

[Jim]

But it's not normal in fact, Windows developers should have
implemented a function that queries computers availability eveytime.
Seeing a non-running computer on a workgroup(previously was on the
lAN) but not accessing it with a error may mean more than one thing.

If Windows queried or refreshed current "real" availabilty of
workgroup computers, we would easily be aware of status of computer 2
if it's really shutdown and left the LAN.

DECnet did this very same thing; DECnet was introduced in the mid 70s. You
could always determine which computers were running.
However, all that glitters isn't gold. To accomplish this task requires
lots of status message through
the network, and the original designers of the Internet Protocol decided not
to burden the network with so many small messages.
Therefore, machines connected via the Internet Protocol only check that the
target is available when the machine has a real live
message to transmit.

The concerns about increased traffic on the internet were lots more
important years ago than they are now.

Jim