Well the subject says it all really.

I do most of my work on a medium-sized network (300 or so machines),
and EVERY single time I open the ntwork explorer, it goes off and
starts trying to show me every single machine on the entire network.

There are actually only one or two domains I'm interested in on this
network, but the only solution is to use the "workgroup" drop down
(who named that?!?!) to stop the damn explorer trying to populate the
world.

And the next time I open the explorer, it's like nothing happened.
It's learned nothing and remembered nothing.

Vista must know there are several domains out there, why doesn't it
just show me those and allow me to drill into them, like XP did. XP
had a MUCH more usable interface for network browsing.

And that's before I get to the stupid problems with NAS devices. Yes,
I know about changing the lmcompatibility level. Why do I have to?

Networking seems to be the single weakest part of Vista.

--
Bob Moore
http://bobmoore.mvps.org/
(this is a non-commercial site and does not accept advertising)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~
Do not reply via email unless specifically requested to do so.
Unsolicited email is NOT welcome and will go unanswered.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~

"Bob Moore" wrote in message
...
.... Networking seems to be the single weakest part of Vista.

Well, that and the new visual navigation "language" that hundreds of
millions of people (by far mostly non-professionals) will have to learn. As
people hear more and more about the downsideS of migrating to Vista, Linux
may have a better chance. It's too bad. I've been a fan of Windows ever
since since v1.1, and even I'm thinking about it.

--
David Dickinson
eveningstar at die-spammer-die dash mvps dot org

Vista Peeve #137: No File Types dialog in Folder Options -- or anywhere!

"Bob Moore" wrote in message
...
Well the subject says it all really.

[snip]

Networking seems to be the single weakest part of Vista.

Oh I wouldn't say THAT.
Lots of other parts of Vista suck enough to pull a melon through a small
drinking straw as well.

Well clearly no-one from MS seems to want to offer any kind of
suggestion as to how I might better use the networking support, or
indeed tell me if it's likely to get better anytime soon (SP1,
anyone?).

I'm not the only person stuck using Vista who thinks the network
explorer is poor to the point of ineptitude, our entire development
team curses at Vista when they have to use this specific feature on
our test system. All the other developers stayed with XP on their
*own* machines, and I don't blame them. Only I stepped up to act as
guinea pig, an act I'm coming to regret.

The rest of Vista is generally OK, we only stumble when forced to use
this part of the system.

--
Bob Moore
http://bobmoore.mvps.org/
(this is a non-commercial site and does not accept advertising)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~
Do not reply via email unless specifically requested to do so.
Unsolicited email is NOT welcome and will go unanswered.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~

I have been scouring the net and forums trying to find a solution to
this very issue. I have been using Vista for a few months now, and
work on a domain of about 300 machines. I'm a software developer that
also unfortunately gets stuck providing tech support for the entire
company. Often this involves hopping over to others' machines to get
files, check out issues, etc. I have agree with Bob Moore. This has
been the single major thorn in my side with Vista (SQL Server
incompatibilities included, but that's another rant). I just don't get
it. It worked *FINE* in XP!! Why did they mess with it? Now, I have
to *WAIT* at least a minute and a half every time I go into Network for
the damned thing to populate!! This is KILLING my productivity. I have
tried disabling IPv6, LLTD, all of that to no avail. Surely SOMEONE at
Microsoft actually goes out to network machines on a regular basis....
hell they must have hundreds of machines on each node.

Does anyone know of a solution to this (aside from going back to XP)??


--
Doc
------------------------------------------------------------------------
Doc's Profile: http://forums.techarena.in/member.php?userid=26717
View this thread: http://forums.techarena.in/showthread.php?t=762618

http://forums.techarena.in

Bob, did you tried to disable the Network Discovery?
Dividing the domain on workgroups also logical and helpfull move.
I have "mesh" network from with XP, Vista and Windows 2000 machines, and I
don't have much troubles with exploring such farm, so my ladies too...

"Bob Moore" wrote in message
...
Well the subject says it all really.

I do most of my work on a medium-sized network (300 or so machines),
and EVERY single time I open the ntwork explorer, it goes off and
starts trying to show me every single machine on the entire network.

There are actually only one or two domains I'm interested in on this
network, but the only solution is to use the "workgroup" drop down
(who named that?!?!) to stop the damn explorer trying to populate the
world.

And the next time I open the explorer, it's like nothing happened.
It's learned nothing and remembered nothing.

Vista must know there are several domains out there, why doesn't it
just show me those and allow me to drill into them, like XP did. XP
had a MUCH more usable interface for network browsing.

And that's before I get to the stupid problems with NAS devices. Yes,
I know about changing the lmcompatibility level. Why do I have to?

Networking seems to be the single weakest part of Vista.

--
Bob Moore
http://bobmoore.mvps.org/
(this is a non-commercial site and does not accept advertising)
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~
Do not reply via email unless specifically requested to do so.
Unsolicited email is NOT welcome and will go unanswered.
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ ~~~~~~~~~~~~~