Johnny

Distinguished
Mar 15, 2001
216
0
18,680
Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

Ports 3 and 4 on my MN-500 have stopped working. Has
anyone else had this to happen? I have tried a soft reset
but have not tried reseting to factory default settings.
 
G

Guest

Guest
Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

Electronic equipment can always die due to a variety of
reasons (e.g. storms, heat...)

In addition to resetting it, unpower the router, wait 3mn
and power it back on (3 to 5 mn is important to let all
components release any electrical charges they may have
accumulated). You may actually want to keep it off for a
while, in case it's a heat problem. Also switch the cables,
in case it's a broken cable.

>-----Original Message-----
>Ports 3 and 4 on my MN-500 have stopped working. Has
>anyone else had this to happen? I have tried a soft reset
>but have not tried reseting to factory default settings.
>.
>
 

joker

Distinguished
Apr 12, 2004
1,064
0
19,280
Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

There was a known problem with firmware versions before 1.08.003 that
ports would die. Usually port 3 was the most robust. Just out of
curiosity what is your firmware version?

Johnny wrote:
> Ports 3 and 4 on my MN-500 have stopped working. Has
> anyone else had this to happen? I have tried a soft reset
> but have not tried reseting to factory default settings.
 
G

Guest

Guest
Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

V1.11.017
I just noticed this problem after the latest software
release last week. Wonder if it's a problem with the ne
firmware?

>-----Original Message-----
>There was a known problem with firmware versions before
1.08.003 that
>ports would die. Usually port 3 was the most robust.
Just out of
>curiosity what is your firmware version?
>
>Johnny wrote:
>> Ports 3 and 4 on my MN-500 have stopped working. Has
>> anyone else had this to happen? I have tried a soft
reset
>> but have not tried reseting to factory default
settings.
>
>.
>
 

joker

Distinguished
Apr 12, 2004
1,064
0
19,280
Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

All I can say is I'm really happy with the 1.08.003 firmware. I'm not
sure I'll upgrade now.

anonymous@discussions.microsoft.com wrote:
> V1.11.017
> I just noticed this problem after the latest software
> release last week. Wonder if it's a problem with the ne
> firmware?
>
>
>>-----Original Message-----
>>There was a known problem with firmware versions before
>
> 1.08.003 that
>
>>ports would die. Usually port 3 was the most robust.
>
> Just out of
>
>>curiosity what is your firmware version?
>>
>>Johnny wrote:
>>
>>>Ports 3 and 4 on my MN-500 have stopped working. Has
>>>anyone else had this to happen? I have tried a soft
>
> reset
>
>>>but have not tried reseting to factory default
>
> settings.
>
>>.
>>
 
G

Guest

Guest
Archived from groups: microsoft.public.broadbandnet.hardware (More info?)

I would be surprised.

I've been using 1.11.017 for the since its release last October and no
problems here with the ports.

It's likely that the ports have suffered some sort of hardware failure. You
should call MSBBN support as they (upon confirming port death) will send you
a new unit if it is still under warranty.

--
Jason Tsang - Microsoft MVP

Find out about the MS MVP Program -
http://mvp.support.microsoft.com/default.aspx

<anonymous@discussions.microsoft.com> wrote in message
news:094501c47ae7$b0412570$a401280a@phx.gbl...
> V1.11.017
> I just noticed this problem after the latest software
> release last week. Wonder if it's a problem with the ne
> firmware?
>
> >-----Original Message-----
> >There was a known problem with firmware versions before
> 1.08.003 that
> >ports would die. Usually port 3 was the most robust.
> Just out of
> >curiosity what is your firmware version?
> >
> >Johnny wrote:
> >> Ports 3 and 4 on my MN-500 have stopped working. Has
> >> anyone else had this to happen? I have tried a soft
> reset
> >> but have not tried reseting to factory default
> settings.
> >
> >.
> >