Just Guessing <(E-Mail Removed)> wrote:
> I am installing SBS 2003. I have discovered that another firm that
> shares the office space has their own router connected piggyback to
> the router of the firm I am contracting with. The other firm has to
> use their router because of HIPPA regulations. I have to call a
> centralized IT group to have it configured.
>
> The firm I'm contracting with doesn't know the username and password
> of their very old Nortel router, so I'm replacing it with something
> new.
>
> I have two nics on my server. Can I connect one router to one nic
> and the other router to the other nic and create a bridge.
Oh, noooo - don't muck around with this. Especially since you're using SBS -
don't make it mad, or it will hurt you.
microsoft.public.windows.server.sbs is the best place for any/all SBS
questions.
> Right now
> the other firm has their router connected to one of the hub ports on
> my firm's router.
>
> Or should I continue to keep the other firms router riding off of my
> firm's router.
I wouldn't. In fact, if the other firm really has to abide by HIPAA
regulations, I'd bet they are not curently compliant.
>
> I guess this boils down to - what the heck do you use bridging for
> anyway?
On a DC/DNS server? Nothing, if you're smart. On an SBS box that isn't
running ISA, I don't even like two NICs at all. It's best to avoid that
configuration on a DC.
To separate the other company's network from yours, if you have to share the
broadband connection, would be something like this (you need at least two
public IPs)
-------------------------------------------------
*ISP's modem/router*
|
|-----Ethernet switch-----|
| |
(123.123.123.1) (123.123.123.2)
*RouterA* *RouterB*
| |
|----LANA----| |----LANB----|
-------------------------------------------------
|