Re: Simultaneous DSL and cable modem access on a SBS network...sorf ot.

Yes, I do mean an actual hub (actually, 2 16 port hubs, one uplinked to
the other). It's what was here when I got here, and it's what's going
to stay in place.

As it stands right now, the cable modem is hooked into the router,
router to hub, hub to everything else (including server.)

So my thinking was that I could add the DSL to the existing hub via a
2nd router, and then the hub would render the idea of two NICs in the
server (which I don't think it has, although I won't know until
tomorrow) unnecessary anyway.

Thanks,



Adam

Blenky wrote:
Problem with not using a Dual WAN port device is that you need to route
the traffic. If you want outbound web going to the cable, then you
would need to route it that way. SBS2003 Standard alone is likely not
going to be possible to set it up that way. I am not sure, but I would
think if you had Premium, you might be able to get it to work, albeit,
it isn't a "normal" configuration. Also, without 2 NICs in your SBS,
how do you plan on bridging the two connections? When you say "hub",
what type of device do you actually mean? I hope not an actual hub...
please say it ain't so! ;-)

In order to know all the port numbers you need open, just run the
Internet Connection wizard on the SBS box, through there there is a
"More Information" button on what ports need to be opened to the SBS.




SEFL wrote:
Thanks, Charlie and Blenky.

Here's the problem with that idea, though, and I really didn't make it
clear in the diagram: The server and the fax (the line the DSL modem
would be hooked up to) are in adjacent rooms...but the cable modem is
approximately 75 feet away across the office itself.

I like the idea, but I can't see it being feasible...assuming I could
even purchase a dual WAN router (I'm in Toronto, and up until you two
mentioned the idea, I never knew they existed...nice idea, though, like
I said.)

The cable modem already has a router attached to it as well, and I was
hoping not to have to waste equipment. I can deal without the failover
(although it would be nice).

I'm also not sure if the SBS has two NICs (we just got it and I haven't
looked at it closely yet...that, and I usually work remotely)...would I
really need them if both routers (or if I can figure out something
else, dual WAN router) went to the hub and then from the hub to the
server?

Thanks.



Adam

Charlie Russel - MVP wrote:
Your best bet here, IMHO, is to use a dual WAN router. Most can handle the
dynamic DNS required on your cable link directly (and if not, you can easily
manage it using something like DirectUpdate), while your static IP address
will come in via DSL. Set your DNS records appropriately, and all should be
fine.

For dual WAN routers, I'm partial to the Xincom line - you do NOT need VPN
capabilities, generally, since your SBS server will usually be the end point
of any VPNs, not the router.


--
Charlie.
http://msmvps.com/xperts64


SEFL wrote:
This is going to sound like a rather oddball scenario, but here goes:

I'm working on a network of about 30 computers inside the network and a
server running Small Business Server 2003 Standard Edition. We're
getting Microsoft CRM put on the server and we need to have a static IP
for it.

The problem is that DSL in the area is not fast enough to support all
of the users and the CRM/Exchange Server simultaneously. And any kind
of a connection that would (5 MB or higher fibre connection) costs in
the 4-digit range, which I can't justify. We do, however, have an
existing cable connection (which doesn't offer true static IP service,
or this would all be solved.)

So...my idea is to use a DSL connection and a cable connection
simultaneously.

I made a diagram outlining what I want to do below:

http://216.89.218.233/public/dsl-cable-diagram.gif

The cable modem already has a router, so I don't need one there. I
would need one for the DSL modem, though, which is fine.

So...here's what I'm thinking of doing:

1) Close all ports on the cable router (since it's not being used for
anything other than web browsing and basic connectivity anyway).

2) Open up whichever ports on the DSL router need to be opened to get
CRM and Exchange Server to work (I don't really know what those are, so
if anyone could help out that way, that'd be great...although I could
find this for myself.)

3) Configure the server to accept traffic from the DSL modem
only...although I'm not 100% sure how to do that either.

Is this logical? And if it is, what would I need to configure on the
SBS to get it to work? The router's not a big deal...just open up
ports or if worse comes to absolute worst create a DMZ for the server
and away we go. But the SBS would be the part that would throw me.

Thanks.



Adam
http://www.searchenginefriendlylayouts.com/

.

Loading