Re: SBS2003 and DSL Modems.

So you're saying this is a static assigned IP address from the ISP but you
have to authenticate using something like PPPOE to connect? The ISPs I use
don't require that type of authentication with a static IP DSL service so
not quite sure what to suggest. Usually with a PPPOE connection its best to
let the router do the authentication rather than some software on the SBS
box doing it.

"TomH" <TomH@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:6717FA59-51B6-42F7-A928-781910DBA9CA@xxxxxxxxxxxxxxxx
> First off, Thanks for reading this post.
>
> I'm a bit new to what I'm trying to do in this post, so if this sounds a
> bit
> simple to some, please pass anything you can along to me.
>
> I am trying to get SBS2003 to play well with a DSL Modem/Router.
>
> The Server has an inside and outside NIC card.
>
> We attempted to get a connection to the Internet two ways.
>
> #1, Connect the DSL Modem to the outside NIC, turn off the router
> functions,
> and let SBS2003 handle all of the connection information. User Name,
> Password and so on. The Modem dials out, but the IP address coming back
> from
> the modem is not the static number that we have. Tried several modems
> from
> the DSL provider, but the problem is between SBS2003 and the DSL Modem.
> Unfortunately the DSL provided will not allow "Other" brands of modems so
> we
> are stuck. This modem will simply not pass on the Static IP address that
> is
> ours, and provides a phantom address, which renders this useless in this
> configuration. So seeing that this will not work, no matter what we try,
> we
> moved to connection #2.
>
> #2, Connect the DSL Modem to the network switch, turn ON the router
> functions, and let the Modem/Router handle all connection information,
> Username, Password and so on. Making sure the Server now knows the
> Internet
> Gateway is the router that is on the switch. This works fine, but we can
> not
> provide for most of the needed functions of SBS2003 from the outside
> world.
> The most we get is Internet to all of the machines. Remote Access, Remote
> Mail, Remote Desktop among other things simply will not work with this
> configuration. We know this. And connecting this configuration to the
> outside NIC also does not work since the Server and the Router functions
> fight with each other and the Static IP again is not passed to the server.
> But the odd thing, the STATIC IP address is showing in this configuration
> but
> will not pass off to the server no matter what we try with Configuration
> #1
> or #2.
>
> This sent us in many directions, and our final thought was to try what we
> are trying now.
>
> I will give a bunch of fake IP numbers just to show what directions we are
> moving in right now.
>
> We have connected the DSL Modem to a Linksys Router BEFSR41.
>
> In the router, DHCP is turned off, and it is given an IP of 192.168.30.1
> We
> have also programmed in the static IP address given by the Modem.
>
> The Linksys router is then connected to the server through its outside NIC
> with an IP address of 192.168.30.2 All pertinent Gateway, Subnet and DNS
> information is programmed into the Linksys Router as well.
>
> The outside NIC on the server is then given the IP of 192.168.30.2,
> Subnet
> of 255.255.255.0, Gateway of 192.168.30.1 (the Linksys Router) and the DNS
> of
> the router 192.168.30.1
>
> And finally, the DMZ of the Linksys Router is turned on for the IP address
> of the Outside NIC of the server. (192.168.30.2)
>
> In theory, what we think should have happened was to basically get by the
> DSL Modem Problem by making the DSL Modem and the LinkSys Router one big
> Cable Modem that just hands over to the server a Static IP address
> (192.168.30.1) from the router, and make it think it's the outside one
> and
> let the router deal with the DSL Modem problem on not handing off our Real
> static IP address.
>
> This works, for about 90% of what we need. We are able to connect to our
> server's remote sites, (http://remote.whatever.com/remote) and we are
> able
> to check mail, and most of the other functions of the remote area, but we
> are
> unable to connect to a remote desktop at all.
>
> When we choose this selection, it sends us the certificate to allow us to
> get into the remote area. Then it displays the lists of machines on the
> network. When we click on one of the machine to remotely work on that
> machine, it does nothing until it ultimately times out.
>
> I know this is a long shot, but has anyone else ever had problems with DSL
> like we have and connecting DSL with SBS2003, or have ever tried what we
> are
> trying. It seems for the most part we are on the right path since we have
> more and more things that we are able to do, but there is something
> missing
> that we can't quite figure out that might be on the Server end or the
> Modem/Linksys end, and we are now stumped.
>
> We can't figure out why SBS2003 will not work with DSL Cable Modems, and
> we
> have also found that there are many people who have the same problems when
> trying to let SBS2003 do the dialing, login and password functions of the
> DSL
> Modem. So we have tried other routes as I have said, with great results
> but
> can not get there 100%.
>
> Thanks to anyone who can shed some light on our problem. I know this is
> not
> something that everyone would or should try, but we are trying to keep
> things
> as secure as possibly and still have our remote access with this stubborn
> DSL
> Modem and Company.
>
> Thanks for all the help!
>


.

Relevant Pages