Sign in with
Sign up | Sign in
Your question

MSN/Qwest Broadband

Last response: in Networking
Share
Anonymous
August 26, 2004 11:08:51 PM

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

I can't get my MN-500 to recognize the existence of an
internet connection. During setup, it swears it's not
there, and -- even after all the appropriate settings have
been maually input -- it still can't see it.

Yet, the main Base Station Management Tool page indicates
I'm connected to the internet, and Windows' own Network
Connections utility says I'm connected (and many bytes are
being exchanged, as also indicated by the lights on my MSN
DSL 1000 modem). The only indication that something's
wrong is on the WAN page of the basestation management
tool where, under WAN Settings - Dynamic, I get this:

Broadband connection: Disconnected (at times it
will say "connecting" but never "connected" that I've seen)
WAN IP address:
Subnet mask:
Default gateway:
Primary Domain Name System (DNS): 205.171.3.65
Secondary DNS: 205.171.2.65

The two above DNS servers were earlier suggested to me by
a particularly hateful person at Qwest DSL
Note that hitting the Release, Renew and Refresh buttons
makes no difference.

KB article 814223 (
http://support.microsoft.com/default.aspx?scid=kb;en-
us;814223 ) addresses MSN broadband problems and I
followed its advice to :

Part 1: Configure WAN
(Under Internet Connection Type, click Dynamic, make sure
there is no host name under Dynamic Connection, click
Clone MAC Address.)

Part 2: Reset Modem

Part 3: Connect Your Base Station

But no change.

My three aspiring network machines are: a VAIO laptop
running on XP Home, another VAIO on XP Pro, and an IPAQ
2215 on WM2003. None of them can connect through the MN-
500, though LAN is functional among all three.

It may not matter, but I'll mention that I might not
actually be on MSN Broadband...Qwest is transitioning
accounts and so while my DSL modem is in fact the MSN DSL
1000, my actual ISP might be Qwest (where they were
previously only the connection to MSN).

Finally, I'm including the following, taken from the
basestation log, chronicling the first few minutes
following one of my MANY unsuccessful setup attempts:
1970/01/01 00:00:00 RF Reset...Pass
1970/01/01 00:00:09 DHCP Client : Send Discover
1970/01/01 00:00:13 DHCP Client : Send Discover
1970/01/01 00:00:20 DHCP Client : Send Discover
1970/01/01 00:00:31 AddPortMapping: ExternalPort:54770,
UDP, InternalPort:12387, InternalClient:192.168.2.30
1970/01/01 00:00:31 AddPortMapping: ExternalPort:33789,
TCP, InternalPort:16181, InternalClient:192.168.2.30
1970/01/01 00:00:35 DHCP Client : Send Discover
1970/01/01 00:01:06 DHCP Client : Send Discover
1970/01/01 00:02:10 DHCP Client : Send Discover
1970/01/01 00:02:22 Wireless client associations SUCCESS,
MAC:0060xxxxxxxx
1970/01/01 00:02:26 Address 192.168.2.33 was assigned to
client 1:0x0060xxxxxxxx
1970/01/01 00:02:31 AddPortMapping: ExternalPort:59614,
UDP, InternalPort:7265, InternalClient:192.168.2.33
1970/01/01 00:02:31 AddPortMapping: ExternalPort:40692,
TCP, InternalPort:13847, InternalClient:192.168.2.33
1970/01/01 00:03:01 Address 192.168.2.33 was assigned to
client 1:0x0060xxxxxxxx
1970/01/01 00:03:01 Address 192.168.2.30 was assigned to
client 1:0x0800yyyyyyyyy
1970/01/01 00:03:01 Address 192.168.2.33 was assigned to
client 1:0x0060xxxxxxxx
1970/01/01 00:03:13 DHCP Client : Send Discover
1970/01/01 00:03:28 192.168.2.30 login successful

Thanks for any help you can offer!

Judd
ps: yes I've installed the MSBN update.

More about : msn qwest broadband

Anonymous
August 27, 2004 1:00:59 PM

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

The Windows network connections utility shows that you are connected because
it is communicating with another network device--in this case the MN-500.

When you take the steps to clone the MAC address, be sure to use the
computer (more specifically the network interface card [NIC]) that you used
to succesfully connect to your DSL modem. Many broadband providers still use
the MAC address (think of it as a serial number for your NIC) to identify
and verify an authentic customer connection.

If you are unable to use that computer or NIC, you'll need to configure the
MAC manually on the configuration page. The MAC address can be found either
via:
--Win9x: Start, Run, winipcfg
--Win2k/XP: Start, Run, cmd, then run command at prompt:\> ipconfig
--linux, unix, BSD, etc--at a command line prompt:# ifconfig

If the NIC is inoperable for some reason, the MAC will also be printed on
the card somewhere, but it may be a little difficult to identify--often the
MAC addresses appear as a just a string of numbers and letters rather than
being pairs delimited by colons (semi-colons, or dashes) as displayed via
ipconfig.

If successful, I would consider removing the DNS servers from your
configuration and letting the MN-500 get them automatically. If your
provider makes some significant changes, these DNS servers could become
unavailable to you and make life difficult again.

-sc


"Judd Bagley" <anonymous@discussions.microsoft.com> wrote in message
news:056701c48bda$cbbc6770$a401280a@phx.gbl...
> I can't get my MN-500 to recognize the existence of an
> internet connection. During setup, it swears it's not
> there, and -- even after all the appropriate settings have
> been maually input -- it still can't see it.
>
> Yet, the main Base Station Management Tool page indicates
> I'm connected to the internet, and Windows' own Network
> Connections utility says I'm connected (and many bytes are
> being exchanged, as also indicated by the lights on my MSN
> DSL 1000 modem). The only indication that something's
> wrong is on the WAN page of the basestation management
> tool where, under WAN Settings - Dynamic, I get this:
>
> Broadband connection: Disconnected (at times it
> will say "connecting" but never "connected" that I've seen)
> WAN IP address:
> Subnet mask:
> Default gateway:
> Primary Domain Name System (DNS): 205.171.3.65
> Secondary DNS: 205.171.2.65
>
> The two above DNS servers were earlier suggested to me by
> a particularly hateful person at Qwest DSL
> Note that hitting the Release, Renew and Refresh buttons
> makes no difference.
>
> KB article 814223 (
> http://support.microsoft.com/default.aspx?scid=kb;en-
> us;814223 ) addresses MSN broadband problems and I
> followed its advice to :
>
> Part 1: Configure WAN
> (Under Internet Connection Type, click Dynamic, make sure
> there is no host name under Dynamic Connection, click
> Clone MAC Address.)
>
> Part 2: Reset Modem
>
> Part 3: Connect Your Base Station
>
> But no change.
>
> My three aspiring network machines are: a VAIO laptop
> running on XP Home, another VAIO on XP Pro, and an IPAQ
> 2215 on WM2003. None of them can connect through the MN-
> 500, though LAN is functional among all three.
>
> It may not matter, but I'll mention that I might not
> actually be on MSN Broadband...Qwest is transitioning
> accounts and so while my DSL modem is in fact the MSN DSL
> 1000, my actual ISP might be Qwest (where they were
> previously only the connection to MSN).
>
> Finally, I'm including the following, taken from the
> basestation log, chronicling the first few minutes
> following one of my MANY unsuccessful setup attempts:
> 1970/01/01 00:00:00 RF Reset...Pass
> 1970/01/01 00:00:09 DHCP Client : Send Discover
> 1970/01/01 00:00:13 DHCP Client : Send Discover
> 1970/01/01 00:00:20 DHCP Client : Send Discover
> 1970/01/01 00:00:31 AddPortMapping: ExternalPort:54770,
> UDP, InternalPort:12387, InternalClient:192.168.2.30
> 1970/01/01 00:00:31 AddPortMapping: ExternalPort:33789,
> TCP, InternalPort:16181, InternalClient:192.168.2.30
> 1970/01/01 00:00:35 DHCP Client : Send Discover
> 1970/01/01 00:01:06 DHCP Client : Send Discover
> 1970/01/01 00:02:10 DHCP Client : Send Discover
> 1970/01/01 00:02:22 Wireless client associations SUCCESS,
> MAC:0060xxxxxxxx
> 1970/01/01 00:02:26 Address 192.168.2.33 was assigned to
> client 1:0x0060xxxxxxxx
> 1970/01/01 00:02:31 AddPortMapping: ExternalPort:59614,
> UDP, InternalPort:7265, InternalClient:192.168.2.33
> 1970/01/01 00:02:31 AddPortMapping: ExternalPort:40692,
> TCP, InternalPort:13847, InternalClient:192.168.2.33
> 1970/01/01 00:03:01 Address 192.168.2.33 was assigned to
> client 1:0x0060xxxxxxxx
> 1970/01/01 00:03:01 Address 192.168.2.30 was assigned to
> client 1:0x0800yyyyyyyyy
> 1970/01/01 00:03:01 Address 192.168.2.33 was assigned to
> client 1:0x0060xxxxxxxx
> 1970/01/01 00:03:13 DHCP Client : Send Discover
> 1970/01/01 00:03:28 192.168.2.30 login successful
>
> Thanks for any help you can offer!
>
> Judd
> ps: yes I've installed the MSBN update.
>
!