OT: WAN Advice
- From: "Amy Babinchak" <amy@xxxxxxxxxxxxxxxxxxxxxxxxxx>
- To: "[ISAserver.org Discussion List]" <isalist@xxxxxxxxxxxxx>
- Date: Sat, 18 Dec 2004 11:28:31 -0500
It's been about 8 years since I last worked in a WAN environment and
about 4 since I last looked at a router and that was only to study for
my little used CCNA. In small business consulting you do a lot of VPN
but rarely a WAN. Rusty but ready. So here's the situation:
Company has 4 offices connected to each other with T1 lines. Each office
has a second T1 for Internet access. There's a Windows 2000 DC at each
location. The main office is called Macomb. (starting to sound like a
test question, eh?) The servers are not able to contact each other and
browsing doesn't work either. Active directory is complaining as is the
licensing service. Users are dropping randomly off the network.
Individuals can get to the Internet sometimes, sometimes not. Workers
are going around the office looking for the computer that can get to the
Internet. They tell me that the network used to work when they were with
XO but since they switched to LDMI they have these problems. To the
users it appears to be intermittent outages; to me it appears that the
routing isn't right.
The T1 to the Internet is connected to a netgear firewall, then to the
switch. The T1 to the Macomb office is connected to a router, then to
the switch.
Looks like this: T1 Macomb - Router
-----------
Switch
T1 Internet - Firewall
They've had two other consultants in there poking around. The first guy
had them buy a new firewall and switches. The second guy removed adware
and junk from the PC's. Neither solved anything.
Here's my thought.
Back in the day we would connect a WAN like this:
T1 Macomb
------------Router - Switch
T1 Internet - Firewall
Am I correct? Shouldn't both T1 lines connect to the router so it can
make the decision whether the request is for the Internet or the WAN?
Amy
Other related posts:
