Networking an "ME" laptop, and an "XP" desktop.

This may sound facetious, but it isn't. After spending about three days
where my XP desktop could see, but not access, my ME laptop, and my ME
laptop would, 90% of the time, refuse to browse the network at all (and 10%
of the time, browse the network but not actually see the desktop); and after
having run right the way through Carrie Holzman's excellent recommendations
page; and having scoured the net for other fixes, I eventually found the
ultimate networking fix for a Toshiba Satellite 1715 CDS - I installed XP
over the top.

Result? Immediate and working, network access. Can't ask for more than that
;-)


Tim

"Tim" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> This may sound facetious, but it isn't. After spending about three days
> where my XP desktop could see, but not access, my ME laptop, and my ME
> laptop would, 90% of the time, refuse to browse the network at all (and
> 10%
> of the time, browse the network but not actually see the desktop); and
> after
> having run right the way through Carrie Holzman's excellent
> recommendations
> page; and having scoured the net for other fixes, I eventually found the
> ultimate networking fix for a Toshiba Satellite 1715 CDS - I installed XP
> over the top.
>
> Result? Immediate and working, network access. Can't ask for more than
> that
> ;-)
>
>
> Tim
>
>

Yeah, I installed XP on my laptop 2 years ago for just that same reason.
However I recently have networked an ME computer to two XP computers
and it went like clockwork. Go figure.

I think networking is more an art than a science and it also depends on how
a computer feels.

Anyway, XP is a much better OS than ME.
Dick Kistler

In article <(E-Mail Removed)>, Tim says...

> This may sound facetious, but it isn't. After spending about three days
> where my XP desktop could see, but not access, my ME laptop, and my ME
> laptop would, 90% of the time, refuse to browse the network at all (and 10%
> of the time, browse the network but not actually see the desktop); and after
> having run right the way through Carrie Holzman's excellent recommendations
> page; and having scoured the net for other fixes, I eventually found the
> ultimate networking fix for a Toshiba Satellite 1715 CDS - I installed XP
> over the top.

> Result? Immediate and working, network access. Can't ask for more than that

Yah, but...your original problem probably related to which computer thought
it was the 'browse master'. In any mix of Windows XP and Windows Me, you
almost always should go to "File and printer sharing for Microsoft
Networks" on the Windows Me computer and disable the 'browse master'
setting. Heck, I do that on my little two-computer network where both
computers are running Windows Me; I disable it on the computer which is on
less often than the other.

--
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint

"N. Miller" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed) om...
> In article <(E-Mail Removed)>, Tim says...
>
>> This may sound facetious, but it isn't. After spending about three days
>> where my XP desktop could see, but not access, my ME laptop, and my ME
>> laptop would, 90% of the time, refuse to browse the network at all (and
>> 10%
>> of the time, browse the network but not actually see the desktop); and
>> after
>> having run right the way through Carrie Holzman's excellent
>> recommendations
>> page; and having scoured the net for other fixes, I eventually found the
>> ultimate networking fix for a Toshiba Satellite 1715 CDS - I installed XP
>> over the top.
>
>> Result? Immediate and working, network access. Can't ask for more than
>> that
>
> Yah, but...your original problem probably related to which computer
> thought
> it was the 'browse master'. In any mix of Windows XP and Windows Me, you
> almost always should go to "File and printer sharing for Microsoft
> Networks" on the Windows Me computer and disable the 'browse master'
> setting. Heck, I do that on my little two-computer network where both
> computers are running Windows Me; I disable it on the computer which is on
> less often than the other.

I thought that the systems could figure out who should be the browse master
on their
own. I haven't messed with that setting on my system, and as of yet haven't
had a
problem. Wired: 1 XP Home, 1 ME Wireless: 1 XP Home. On a ptp network
setting a computer to be the browse master would require it to be on,
wouldn't it.
That would be damned inconvienient.

Dick Kistler

>
> --
> Norman
> ~Win dain a lotica, En vai tu ri, Si lo ta
> ~Fin dein a loluca, En dragu a sei lain
> ~Vi fa-ru les shutai am, En riga-lint

In article <#(E-Mail Removed)>, Dick Kistler says...

> "N. Miller" <(E-Mail Removed)> wrote in message
> news:(E-Mail Removed) om...
> > In article <(E-Mail Removed)>, Tim says...

> >> This may sound facetious, but it isn't. After spending about three days
> >> where my XP desktop could see, but not access, my ME laptop, and my ME
> >> laptop would, 90% of the time, refuse to browse the network at all (and
> >> 10%
> >> of the time, browse the network but not actually see the desktop); and
> >> after
> >> having run right the way through Carrie Holzman's excellent
> >> recommendations
> >> page; and having scoured the net for other fixes, I eventually found the
> >> ultimate networking fix for a Toshiba Satellite 1715 CDS - I installed XP
> >> over the top.

> >> Result? Immediate and working, network access. Can't ask for more than
> >> that

> > Yah, but...your original problem probably related to which computer
> > thought
> > it was the 'browse master'. In any mix of Windows XP and Windows Me, you
> > almost always should go to "File and printer sharing for Microsoft
> > Networks" on the Windows Me computer and disable the 'browse master'
> > setting. Heck, I do that on my little two-computer network where both
> > computers are running Windows Me; I disable it on the computer which is on
> > less often than the other.

> I thought that the systems could figure out who should be the browse master
> on their
> own. I haven't messed with that setting on my system, and as of yet haven't
> had a
> problem. Wired: 1 XP Home, 1 ME Wireless: 1 XP Home. On a ptp network
> setting a computer to be the browse master would require it to be on,
> wouldn't it.
> That would be damned inconvienient.

If it works in automatic mode, don't mess with it. But in a case like mine,
were one is on most of the time anyway, it doesn't hurt. But in a mix of
Windows XP and Windows Me, it seems that the XP insists on being the browse
master, but if the Me machine is on more often, it forgets to look. Or
something like that. I can't speak from personal experience about the XP /
Me combo, though...

--
Norman
~Win dain a lotica, En vai tu ri, Si lo ta
~Fin dein a loluca, En dragu a sei lain
~Vi fa-ru les shutai am, En riga-lint