Internet Access Problems

[Guest]

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

I have a Base Station 700. It is connected to the Internet via a
cable modem to Cox. We have a W2k3 server sitting on the LAN behind
the Base Station.

I can get _to_ our W2K3 server from the Internet, but right now cannot
get _from_ the server to the Internet.

TSing into the server, I can ping the internal (LAN) IP address of the
Base Station, but cannot ping the Base Station's external IP address.
I can ping other hosts on the LAN.

From an external host, I can ping the external IP address of the Base
Station. The problem appears after the server has been up and running
for several days. And if I reboot the server, the problem usually
goes for a those couple of days.

One thing I noticed is that the hardware (MAC) address of the Base
Station is shown as different numbers between when I do and arp -a on
the server and what is reported by the Base Station istelf through the
management tool.

The difference is in the first pair of numbers of the MAC address -
part of the manufacturer's identification. On the management tool
this is shown as 00- and in the arp is shows up as 02-. I suspect
this might just be a bug in the management tool software, or it could
be a real problem.

----- Base station information -----
Runtime code version: 02.00.07.0331
Boot code version: 02.00.07.0331
LAN MAC address: 00-0D-3A-2C-04-63
MAC address: 00-0D-3A-2C-04-62
Serial number: 468091094795
Hardware version: 00.00.00.0004

------ arp from server --------
C:\>arp -a

Interface: 192.168.2.2 --- 0x10003
Internet Address Physical Address Type
192.168.2.1 02-0d-3a-2c-04-63 dynamic

Can anyone tell, from my description, what the problem is and how I
can fix it?

Thanks

--
Matt Hickman

 

[joker]

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

With your version of the firmware (the version the hardware came with)
the MN-700 doesn't have loopback support. This means you can't connect
to the WAN IP from behind the MN-700 unless you upgrade your firmware
version. The current version 2.01.02.0590 does have loopback support &
fixes several other issues with the MN-700. I strongly recommend that
you download it & install it.

You can get it at the following address

MSBNDownload (This is the update package. It will update software
(including drivers) and firmware as needed)

http://download.microsoft.com/download/8/d/5/8d5f3570-e0aa-4ac4-8448-579870373a0f/MSBNDownload.exe

(note that this URL is very long and might get truncated)

Matt Hickman wrote:

> I have a Base Station 700. It is connected to the Internet via a
> cable modem to Cox. We have a W2k3 server sitting on the LAN behind
> the Base Station.
>
> I can get _to_ our W2K3 server from the Internet, but right now cannot
> get _from_ the server to the Internet.
>
> TSing into the server, I can ping the internal (LAN) IP address of the
> Base Station, but cannot ping the Base Station's external IP address.
> I can ping other hosts on the LAN.
>
> From an external host, I can ping the external IP address of the Base
> Station. The problem appears after the server has been up and running
> for several days. And if I reboot the server, the problem usually
> goes for a those couple of days.
>
> One thing I noticed is that the hardware (MAC) address of the Base
> Station is shown as different numbers between when I do and arp -a on
> the server and what is reported by the Base Station istelf through the
> management tool.
>
> The difference is in the first pair of numbers of the MAC address -
> part of the manufacturer's identification. On the management tool
> this is shown as 00- and in the arp is shows up as 02-. I suspect
> this might just be a bug in the management tool software, or it could
> be a real problem.
>
> ----- Base station information -----
> Runtime code version: 02.00.07.0331
> Boot code version: 02.00.07.0331
> LAN MAC address: 00-0D-3A-2C-04-63
> MAC address: 00-0D-3A-2C-04-62
> Serial number: 468091094795
> Hardware version: 00.00.00.0004
>
> ------ arp from server --------
> C:\>arp -a
>
> Interface: 192.168.2.2 --- 0x10003
> Internet Address Physical Address Type
> 192.168.2.1 02-0d-3a-2c-04-63 dynamic
>
> Can anyone tell, from my description, what the problem is and how I
> can fix it?
>
> Thanks
>

 

[Guest]

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

joker <no-spam@netzero.com> wrote in message news:<#HyqAlEcEHA.3864@TK2MSFTNGP10.phx.gbl>...
> With your version of the firmware (the version the hardware came with)
> the MN-700 doesn't have loopback support. This means you can't connect
> to the WAN IP from behind the MN-700 unless you upgrade your firmware
> version. The current version 2.01.02.0590 does have loopback support &
> fixes several other issues with the MN-700. I strongly recommend that
> you download it & install it.
>
I upgraded the MN-700 firmware. Hopefully this will fix the Internet
access routing.

It may have something to do with the DHCP issues the
fix repairs. After writing my original article and before applying the fix,
we rebooted the server again, and still had problems. Then we modified
the DHCP configuration on the MN-700, Internet access was restored.

I should know in a few days. However, I still cannot
ping the external address of the router from the server.

Thanks,

--
Matt Hickman
...when faced with a problem you do not understand, do any part of it
you do understand, then look at it again.
Robert A. Heinlein (1907 - 1988)
_The Moon Is a Harsh Mistress_ c 1966

 

[Guest]

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

joker <no-spam@netzero.com> wrote in message news:<#HyqAlEcEHA.3864@TK2MSFTNGP10.phx.gbl>...
> With your version of the firmware (the version the hardware came with)
> the MN-700 doesn't have loopback support. This means you can't connect
> to the WAN IP from behind the MN-700 unless you upgrade your firmware
> version. The current version 2.01.02.0590 does have loopback support &
> fixes several other issues with the MN-700. I strongly recommend that
> you download it & install it.

The firmware upgrade fixed it. The problem was probably related to
the DHCP issue addressed in the upgrade, and it has not re-appeared since
the upgrade was installed.

Thanks.

--
Matt Hickman
It is never safe to laugh at Dr. Malthus; he always has the
last laugh. A depressing man. I'm glad he is dead.
Robert A. Heinlein (1907 - 1988)
_The Moon Is a Harsh Mistress_ c 1966