MN-710 fails to restablish connection after reboot

Like the subject line says, MN-710 fails to restablish
connection after reboot.

I've tried with and w/out the MBNU, the Network wizard.
Most times the only thing that works is to first unplug
the card then run the MNBU or the wizard.(If one fails
the other works) This was random initially now persistent.

I connect through a wireless D-link router which is
configured as the DHCP server. When I reboot the card
configures itself, 169.xxx.xxx.xxx. It's as if it
completely ignores the router. I have the DNS client
service disabled.

Side Note: After rebooting the MNBU shows the LAN SSID as
connected to the AP but with an internal/self assigned IP
but I cannot connect to other workstations or the net.

Thanks in advance...


Michael Ninos

It's the BIOS on the USB controller (if you use an add-in card) or the
BIOS on the motherboard that is the problem. You might try updating the
buggy BIOS. If that doesn't fix the issue you will most likely have to
replace the hardware that is causing the problem. (This means the
MN-710 is fine but your computer has some crappie hardware on it.)

Michael Ninos wrote:

> Like the subject line says, MN-710 fails to restablish
> connection after reboot.
>
> I've tried with and w/out the MBNU, the Network wizard.
> Most times the only thing that works is to first unplug
> the card then run the MNBU or the wizard.(If one fails
> the other works) This was random initially now persistent.
>
> I connect through a wireless D-link router which is
> configured as the DHCP server. When I reboot the card
> configures itself, 169.xxx.xxx.xxx. It's as if it
> completely ignores the router. I have the DNS client
> service disabled.
>
> Side Note: After rebooting the MNBU shows the LAN SSID as
> connected to the AP but with an internal/self assigned IP
> but I cannot connect to other workstations or the net.
>
> Thanks in advance...

You are an obviously arrogant individual who does not
take the time to research or investigate before you flame
someone.

While searching for an answer here for my issue I read
several posts where you assume your information is law.
Without further information from the individual posting,
I find it impossible to diagnose exactly what the
solution is. Unless you have addressed the identical
issue, there are simply too many hardware/software
configurations.

If you had taken the time to research possible
causes/solutions you would be aware of the update to the
MBNU that has solved the issue.

Unprofessional and rude, that will always lead to gaining
success while earning respect.

>-----Original Message-----
>It's the BIOS on the USB controller (if you use an add-
in card) or the
>BIOS on the motherboard that is the problem. You might
try updating the
>buggy BIOS. If that doesn't fix the issue you will most
likely have to
>replace the hardware that is causing the problem. (This
means the
>MN-710 is fine but your computer has some crappie
hardware on it.)
>
>Michael Ninos wrote:
>
>> Like the subject line says, MN-710 fails to restablish
>> connection after reboot.
>>
>> I've tried with and w/out the MBNU, the Network
wizard.
>> Most times the only thing that works is to first
unplug
>> the card then run the MNBU or the wizard.(If one fails
>> the other works) This was random initially now
persistent.
>>
>> I connect through a wireless D-link router which is
>> configured as the DHCP server. When I reboot the card
>> configures itself, 169.xxx.xxx.xxx. It's as if it
>> completely ignores the router. I have the DNS client
>> service disabled.
>>
>> Side Note: After rebooting the MNBU shows the LAN SSID
as
>> connected to the AP but with an internal/self assigned
IP
>> but I cannot connect to other workstations or the net.
>>
>> Thanks in advance...
>
>.
>

Well I guess I will never help you again. Also I have over 18 moths
experience working for Microsoft. Besides 3+ years elsewhere in
Computer support related jobs. You think my confidence is arrogance.
It is the fact that I have extensive knowledge of the OS and how it
operates. So grow up little boy if you don't like my attitude.

Michael Ninos wrote:

> You are an obviously arrogant individual who does not
> take the time to research or investigate before you flame
> someone.
>
> While searching for an answer here for my issue I read
> several posts where you assume your information is law.
> Without further information from the individual posting,
> I find it impossible to diagnose exactly what the
> solution is. Unless you have addressed the identical
> issue, there are simply too many hardware/software
> configurations.
>
> If you had taken the time to research possible
> causes/solutions you would be aware of the update to the
> MBNU that has solved the issue.
>
> Unprofessional and rude, that will always lead to gaining
> success while earning respect.
>
>
>>-----Original Message-----
>>It's the BIOS on the USB controller (if you use an add-
>
> in card) or the
>
>>BIOS on the motherboard that is the problem. You might
>
> try updating the
>
>>buggy BIOS. If that doesn't fix the issue you will most
>
> likely have to
>
>>replace the hardware that is causing the problem. (This
>
> means the
>
>>MN-710 is fine but your computer has some crappie
>
> hardware on it.)
>
>>Michael Ninos wrote:
>>
>>
>>>Like the subject line says, MN-710 fails to restablish
>>>connection after reboot.
>>>
>>>I've tried with and w/out the MBNU, the Network
>
> wizard.
>
>>>Most times the only thing that works is to first
>
> unplug
>
>>>the card then run the MNBU or the wizard.(If one fails
>>>the other works) This was random initially now
>
> persistent.
>
>>>I connect through a wireless D-link router which is
>>>configured as the DHCP server. When I reboot the card
>>>configures itself, 169.xxx.xxx.xxx. It's as if it
>>>completely ignores the router. I have the DNS client
>>>service disabled.
>>>
>>>Side Note: After rebooting the MNBU shows the LAN SSID
>
> as
>
>>>connected to the AP but with an internal/self assigned
>
> IP
>
>>>but I cannot connect to other workstations or the net.
>>>
>>>Thanks in advance...
>>
>>.
>>

MS employees post their credintials, where are yours? I
will not waste my time arguing with you but it is obvious
that you are not a professional in the least. As I stated
in prior posts, I have read several of your posts. I
agree that you have some knowledge above the average user
but your approach is reprehensible.

I do have one question, did you use the line, have dealt
with "crappie hardware/BIOS for 18 moths" on your
resume? How long exactly is a "moth."

As an MS employee, you should be aware of spell check.
Maybe you should try it sometime.


>-----Original Message-----
>Well I guess I will never help you again. Also I have
over 18 moths
>experience working for Microsoft. Besides 3+ years
elsewhere in
>Computer support related jobs. You think my confidence
is arrogance.
>It is the fact that I have extensive knowledge of the OS
and how it
>operates. So grow up little boy if you don't like my
attitude.
>
>Michael Ninos wrote:
>
>> You are an obviously arrogant individual who does not
>> take the time to research or investigate before you
flame
>> someone.
>>
>> While searching for an answer here for my issue I read
>> several posts where you assume your information is
law.
>> Without further information from the individual
posting,
>> I find it impossible to diagnose exactly what the
>> solution is. Unless you have addressed the identical
>> issue, there are simply too many hardware/software
>> configurations.
>>
>> If you had taken the time to research possible
>> causes/solutions you would be aware of the update to
the
>> MBNU that has solved the issue.
>>
>> Unprofessional and rude, that will always lead to
gaining
>> success while earning respect.
>>
>>
>>>-----Original Message-----
>>>It's the BIOS on the USB controller (if you use an add-
>>
>> in card) or the
>>
>>>BIOS on the motherboard that is the problem. You
might
>>
>> try updating the
>>
>>>buggy BIOS. If that doesn't fix the issue you will
most
>>
>> likely have to
>>
>>>replace the hardware that is causing the problem.
(This
>>
>> means the
>>
>>>MN-710 is fine but your computer has some crappie
>>
>> hardware on it.)
>>
>>>Michael Ninos wrote:
>>>
>>>
>>>>Like the subject line says, MN-710 fails to
restablish
>>>>connection after reboot.
>>>>
>>>>I've tried with and w/out the MBNU, the Network
>>
>> wizard.
>>
>>>>Most times the only thing that works is to first
>>
>> unplug
>>
>>>>the card then run the MNBU or the wizard.(If one
fails
>>>>the other works) This was random initially now
>>
>> persistent.
>>
>>>>I connect through a wireless D-link router which is
>>>>configured as the DHCP server. When I reboot the card
>>>>configures itself, 169.xxx.xxx.xxx. It's as if it
>>>>completely ignores the router. I have the DNS client
>>>>service disabled.
>>>>
>>>>Side Note: After rebooting the MNBU shows the LAN
SSID
>>
>> as
>>
>>>>connected to the AP but with an internal/self
assigned
>>
>> IP
>>
>>>>but I cannot connect to other workstations or the net.
>>>>
>>>>Thanks in advance...
>>>
>>>.
>>>
>
>.
>

"Michael Ninos" <(E-Mail Removed)> wrote in message
news:9e5001c4790e$5ae7cbe0$(E-Mail Removed)...
> You are an obviously arrogant individual who does not
> take the time to research or investigate before you flame
> someone.
> .
> .
> Unprofessional and rude, that will always lead to gaining
> success while earning respect.

Yeah, that's exactly what I was thinking ... Oh, wait ... you were talking
about Joker? Wow ... I've heard certain drugs aggravate projective
personality disorders. I'd suggest maybe laying off the crackpipe.

*shrug*
Mark