Modem in bridge mode v. Windows

At home I have a D-LINK DSL300T ethernet modem connected via Homeplug
to a NIC on a box running Windows Server 2003. The other NIC on the
server supports a LAN serving the rest of the house.

The network adds a little oddly, in that sometimes the Internet side
of the server gets allocated an address on the same subnet as the
'management' address in the modem, and at other times it is getting
the public IP. This confusion results in unreliable resonse times,
with DNS lookups in particular often failing on the first try.

The modem can be run in bridged mode, with NAT and DHCP turned off.
Can Server 2003 then drive this connection properly? Is it simply a
case of selecting 'Connect using a broadband connection that requires
a user name' and filling that in?

On 22 May, 17:42, Ken Wheatley <k...@birchanger.com> wrote:

> The network adds a little oddly, in that sometimes the Internet side
> of the server gets allocated an address on the same subnet as the
> 'management' address in the modem, and at other times it is getting
> the public IP. This confusion results in unreliable resonse times,
> with DNS lookups in particular often failing on the first try.

that's a consequence of the kludge used to get the external IP to the
server by a short duration DHCP lease, once the "modem" (which is a
router really) gets the external IP it passes it over.

If your ISP supports PPPoE then the other mode you describe may work.
Otherwise run it as a proper router.

Phil