I have exactly the same problem. I purchased a MN-700
base station over Boxing Week, and am using it to connect
a desktop running Win98 and wireless "b" laptop to my DSL
modem. My desktop, which is connected to the MN-700 via
an ethernet connection has no problems connecting with the
internet.
However, i have frequent wireless connection issues with
my laptop. I only have 1 bedroom apartment, so either i'm
in the same room as my basestation or in the next room.
Yet my internet connection will also periodically
disconnect (even tho signal strength is excellent) or lose
the wireless network connection altogether.
I have tried many of the same things that you and other
users have also done, but with no luck.
What is infuriating is because I purchased the MN-700 b/c
I also initially purchased one for my family's home during
X-mas break, and it worked well with my laptop. So I
decided to purchase another for my own use. However, my
parent's use a Cable modem, not DSL.
i hope to return this product as it doesn't not work well
with DSL PPPoE modems.
Sincerely,
CW
>-----Original Message-----
>Hello,
>
>I've spent the last two days unsucessfully
troubleshooting an MN-700
>wireless access point with an MN-520 "b" adapter and an
MN-730 "g"
>adapter.
>
>Today I went through the MS support process for the issue
with no
>luck.
>
>Here is my current setup: MN-700 running in mixed mode,
as an access
>point. I have disabled WEP and WPA completely and am
running with no
>authentication. I do limit connections based on MAC
address, and this
>functionality works fine. I have two client PCs each
running Windows
>XP Professional. One is an HP Laptop with an MN-520 "b"
adapter, the
>other is an HP Desktop with an MN-730 "g" adapter.
>
>My circumstance is that, even now, as I sit with the
laptop
>approximately 24 inches from the base station I get
periodic
>disconnections from the base station. They last just
seconds, and if
>I "wait-it-out", it works fine again in about 5-10
seconds with no
>intervention on my part. If I disconnect the PCMCIA card
and
>immediately reconnect it the connection is picked up
virtually
>instantly. It's quite a nice little problem. In a bad
way. This is
>my second such PCMCIA adapter. The same problem is
present on either
>adapter.
>
>I've updated the firmware on the base station. By the
way, this was a
>major hassle since it can only be done via a wired
connection. Very
>taxing. I was required to actually go out and buy a
standard ethernet
>card, install that, buy an appropriate ethernet cable and
then do the
>update since the utility will not allow updates to be
done wirelessly.
> This update was done as of today and the boot-code as
well
>runtime-code version numbers on the MN-700
report "02.00.08.0333".
>
>I have completely disconnected and discarded a perfectly
good wireless
>phone on MS's demand, yet the problem still continues.
There are no
>other known interference points.
>
>Okay, so, there. That's the problem. Now, I've been
through these
>newsgroups going back since the MN-700 was released. And
I've seen
>lots and lots of similiar people with the same exact
problem, or very
>similiar problems.
>
>So, now, the place of purchase that I bought the MN-700
will not
>accept the return. They claim that everything is fine,
if there are
>quality issues with the product I should take them up
with Microsoft.
>Fine, but well, it's not fine.
>
>While dealing with several MS rep's today I took the
liberty of
>recording the conversations with my PC. Just so everyone
knows, this
>is legal in my state so long as one party knows that the
call is being
>recorded (i.e., me, the person doing the recording). I
have well over
>3 hours of data on this topic, and well, frankly, I
caught virtually
>every single MS employee I dealt with today in some sort
of lie,
>fabrication, bogus finger-pointing, or distortion. A
sampling:
>
>1. An MS employee told me this was a confirmed issue
with my specific
>model of laptop. I was best off contacting the vendor
for help.
>After instructing him that I hadn't told him the make or
model of my
>laptop, he mumbled and trailed off about his notes.
>
>2. Another MS employee told me this was a result of an
authentication
>problem because I faultily enabled 802.1x
authentication. After
>reminding him that I in fact was not running any WEP at
all, he barked
>at me that I never told him that. The tape clearly shows
otherwise.
>
>3. Another MS employee on a later call told me that
there was nothing
>I could do, that this was just how wireless networks
are. This is, of
>course, not true. Wireless networks do not simply
disconnect the user
>after a few minutes of use for no reason.
>
>4. Yet another MS employee told me that I was running an
out-of-date
>version of Windows XP. Untrue. Every patch is applied,
it is
>perfectly current. He then also implied I was running an
illegal copy
>of XP and that the software knew this and was punishing
me. Also,
>again, untrue. I am not running an illegal copy of XP,
and even if I
>were, I doubt the software would be punishing me in the
manner.
>
>5. A person identified as a supervisor took my call
after a bit on
>hold. He told me that notebook adapter must be
defective. I should
>exchange for a new one. I instructed him that is the
second one I've
>tried, and that the store I purchased the units would
accept no
>exchanges nor provide refunds. He called me a liar.
Straight out, no
>footwork. "I think you are lying. That's not true."
For measure I
>returned to the store and got the service manager telling
me on tape
>that he would not accept returns or refunds, that I must
deal with MS
>for defective/poor quality hardware.
>
>I have many many more issues with their tech support. I
was on hold
>for long periods. Many of the reps spoke broken or poor
or virtually
>no english what-so-ever.
>
>As a result of these issues, I contacted my state
attorney's office,
>as well as my family attorney. I am posting this message
as a call
>for other owners to please post their own stories here on
this thread.
> In my state and most states it is illegal to sell
products with
>defects in workmanship. It is my opinion that the MN-
700 - or a
>high-number of them - are defective. I am pursuing a
legal case on
>the matter - both as a criminal and a civil matter at
this point -
>against Microsoft, the maker of the MN-700. The product
is
>unacceptable. Continuing to sell it is an affront to my
good senses
>and a slap in the face of the people trying to get their
units working
>at all.
>
>If any of this sounds familiar, post your story below. I
have a
>meeting with my state attorney and personal attorney in
10 days and I
>will present my story and evidence along with that of
anyone else who
>feels obliged to post here.
>
>Regards,
>Dan Heskett
>.
>
Similar Threads
Linear Mode
