intermittant connections

I am having problems with WinME connecting to a Pipeline
85 Router. Sometimes it connects, sometimes it doesn't.
Re-starting the computer doesn't seem to make any
difference, and re-setting the router doesn't seem to make
any difference, either. A laptop running XP never has any
problem connecting. Is there some common problem with ME
that can be fixed ?

In article <1a1c01c47c62$9ec55bf0$(E-Mail Removed)>, Ace says...

> I am having problems with WinME connecting to a Pipeline
> 85 Router. Sometimes it connects, sometimes it doesn't.
> Re-starting the computer doesn't seem to make any
> difference, and re-setting the router doesn't seem to make
> any difference, either. A laptop running XP never has any
> problem connecting. Is there some common problem with ME
> that can be fixed ?

Nope. No "common problem", anyway. It is all in the configuration of
adapters, protocols, clients, and services. Windows Me does not seem to be
much different from Windows 98SE, or Windows XP; at least not when I get my
hands on my brother-in-law's network. I have always managed to get him going
again after he has broken it.

You have checked the cabling, and other hardware, I take it?

--
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

Yes, cables have been used on XP machine, never a
problem. NIC is new D-Link 530+. Have double-checked
seating in PCI slot, seems OK.

Thanks for response, but still wondering.


>-----Original Message-----
>In article <1a1c01c47c62$9ec55bf0$(E-Mail Removed)>, Ace
says...
>
>> I am having problems with WinME connecting to a
Pipeline
>> 85 Router. Sometimes it connects, sometimes it
doesn't.
>> Re-starting the computer doesn't seem to make any
>> difference, and re-setting the router doesn't seem to
make
>> any difference, either. A laptop running XP never has
any
>> problem connecting. Is there some common problem with
ME
>> that can be fixed ?
>
>Nope. No "common problem", anyway. It is all in the
configuration of
>adapters, protocols, clients, and services. Windows Me
does not seem to be
>much different from Windows 98SE, or Windows XP; at least
not when I get my
>hands on my brother-in-law's network. I have always
managed to get him going
>again after he has broken it.
>
>You have checked the cabling, and other hardware, I take
it?
>
>--
>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 <1fca01c47d32$21e9e530$(E-Mail Removed)>, Ace says...

> Yes, cables have been used on XP machine, never a
> problem. NIC is new D-Link 530+. Have double-checked
> seating in PCI slot, seems OK.

> Thanks for response, but still wondering.

Hmmm. Interesting thought; do you have "File and printer sharing for
Microsoft Networks" installed. If so, is the Windows Me 'browse master'
setting anything other than 'disabled'? With a Windows XP machine in the
loop, I believe that the XP machine automatically becomes the 'browser
master', and the Windows Me machine may choke if it also tries to be the
'browse master'. This may actually be the "Windows Me" unique problem that
you are wondering about.

In my small, two computer, home LAN I have two Windows Me computers. I have
an MTA running on one, so it stays on more often than the other. In my case,
I have set the computer which is on most often as the default 'browse
master', and then disable 'browse master' on the other. I don't seem to have
an difficulty in this way.

I don't know if it would be better to enable 'browse master' on your Me
computer, and disable it on the XP computer, or the other way around. Maybe
one of the MVPs will stumble into this thread and weigh in with an opinion.

--
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

Well, I ended up solving my problem by re-locating my D-
link NIC to another PCI slot, and downloaded a new driver
for it that supported NDIS 4 & 5. After re-booting, I re-
set my IP addresses for the router and ISP. Everything
works now.

Thanks for all replys !


>-----Original Message-----
>I am having problems with WinME connecting to a Pipeline
>85 Router. Sometimes it connects, sometimes it doesn't.
>Re-starting the computer doesn't seem to make any
>difference, and re-setting the router doesn't seem to
make
>any difference, either. A laptop running XP never has
any
>problem connecting. Is there some common problem with ME
>that can be fixed ?
>.
>

In article <9D106ED1-5CC9-480C-AF57-(E-Mail Removed)>, =?Utf-8?B?
QnJ1Y2VfTW9ycmlz?= says...

> In a separate post 16 Aug 04...

You couldn't find a way to post this to the original thread? Message ID$ of
that post? Do you expect me to dig through all the messages to find it?
Hmmm. Searched, didn't find a "separate" post. Or, did you mean that this
one is to be considered separate? Oops. The nature of NNTP service, even
when linked with Web browsers through the Microsoft CDO for Windows 2000, is
to thread posts by Message-ID$, if the poster uses the "Reply" button
instead of the "New Post" button.

> I reported my problem with inconsistent WinMe
> accessability via IE through a LinkSys WAPR on a home LAN with a second Win
> XP Home system. The WinXP accessability is consistently good, but that for
> the WinMe system is very inconsistent. I have been able to access only
> Google search results for "windowsupdate" and a Sympatico-MSN search results
> for the same, plus some other search results. However, the WinME system will
> not connect to either the Windows Update site, or the MS Hotmail site. Given
> the responses from Norman, that there does not appear to be a "common WinMe
> problem", I would appreciate any insight that anyone can offer to provide a
> solution. I have not made any recent changes to any part of my home
> networked system.

You can access some sites, but not all sites on the affected computer.

http://www.google.com/ yes
http://sympatico.msn.ca/ yes

http://v4.windowsupdate.microsoft.com/en/default.asp no
http://login.passport.net/uilogin.srf?id=2 no

I don't see a networking issue at all, here. If your LAN was broken, all
four URLs should be a "no". Something else is afoot. Firewall, maybe. Bad
entries in the 'hosts' file, maybe. A local proxy, like Promomitron,
misconfigured, maybe. A browser hijacker, maybe.

But nothing that fiddling with the Network properties will fix.

--
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