On Wed, 29 Mar 2006 12:28:05 -0800, rick s wrote:

Hi,
I am helping my neighbor convert from dial up to SBC DSL. The line was
brought up and we installed all the filters in the house. The DSL came with a
Speed Strem 4100 modem. This modem looks like a high speed connection to the
PC not a broadband connection. We followed all the directions and brought the
PC up. The main problem is that after the PC comes up from being powered down
and you start IE you are unable to make a connection. If you restart the PC ,
without powering it off, you are ok until you power off and then you have to
do a system restart to get it to work. The PC is running Windows ME and is up
to current maintenance. I am running AVG and Zone Alarm. But it fails even if
I don't have them up.
I took my Speed Strem 5360 from at home and connected it on the ME PC. This
uses a broadband connect that uses the program to start and stop the
connection sending a ID and Password. Using this configuration IE works just
fine.
I took their 4100 modem to my house and connected it and it works fine, but
I am using windows XP.
Any ideas what I need to due to make ME work after a power up.

Your SS5360 is a bridged modem. Your neighbor's SS4100 is a bit fancier,
being able to initiate a PPPoE login session from the modem. This is not an
MSFT thing, but a Siemens/SBC thing. Best place I can think of to help
would be he

http://www.dslreports.com/forum/ilec,am

If there is no router involved, you would either need a connection manager
(something like "RASPPPoE") on the computer, or you would connect to the
modem using http://192.168.0.1/, and enter the PPPoE log in information on
the computer. Either method should work. You will get more details at the
site above.

Actually, to elaborate a bit, the SBC-issued SS4100 DSL Modem can be
accessed from a web browser at:

http://192.168.0.1/

For no router:

If you don't do anything to this modem out of the box, not even access it
via the browser, and just run the SBC provided connection manager (for
Windows 98/ME/2K; Windows XP includes a PPPoE connection manager, so don't
use a different one), the modem will start up in bridged mode
automatically. When you run the connection manager, that will log in the
DSL session. The status lights, upon synch, will be:

Power - Green
Ethernet - Green
DSL - Green
Internet - Unlit
Activity - Flash with data flow

In this configuration, the connection is lost when the computer is shut
down.

If you decide to put the PPPoE login information in the modem, it will
initiate the PPPoE login, and you won't need the connection manager on the
computer.

The modem default is then "PPP is on the modem, use a public IP address".
When you start up the modem, after it synchs to the DSLAM, it will initiate
the PPPoE login. At this point, the modem will present the public IP
address on the Ethernet port; any connected device will pull it when set to
obtain an IP address automatically. When a computer is booted, the modem
status lights will be:

Power - Green
Ethernet - Green
DSL - Green
Internet - Green
Activity - Flash with data flow

If you change the modem from the default to "PPP is on the modem, use a
private IP address", everything will be the same as for passing through the
public IP address with one exception; the device will be assigned
192.168.1.64 instead of the public IP address.

If you add a router, you would configure the router to obtain an IP address
automatically on the WAN side; this is the same choice as a cable customer
would use. If you change the router LAN IP address to 192.168.x.1, where
'x' is from '1' to '255', you will be able to access the modem
configuration pages in a web browser through the router. Any applications
requiring that unsolicited packets be accepted from the Internet will see
this rig as a "cascaded NAT" (or, by popular terminology, "double NAT").

One important note needs to be stressed; if the modem is running in NAT
mode, it _will_ pass all unsolicited packets through without doing some
non-supported trickery. This is a modem, which uses DHCP to assign an IP
address (as in _ONE_ IP address); whether it is the public IP address, or
the NAT IP address 192.168.1.64, there is _NO_ firewall. No packet
filtering. No SPI. You are as exposed as if this were a bridged modem! And
there is no way to change either the modem IP address (192.168.0.1), or the
private IP address assigned by the DHCP server (192.168.1.64).

--
Norman
~Oh Lord, why have you come
~To Konnyu, with the Lion and the Drum