ddrueding
Fixture
I have a company with three locations. Each is being served by a cable modem connected to a WRT54GL that establishes the VPN link between them. At each office is a Server 2003R2 machine acting as DC, DNS, DHCP, and DFS. Everything is working as expected except the DFS. It tends to not like files larger than 90MB; only replicating them one way or not at all in a sporadic fashion.
I'm trying to put together some kind of monitoring package, something that could give useful information about the health/status of the VPN/DFS links. Things I would like to know:
1. Internet (up/down/bandwidth consumed)
2. VPN (up/down/bandwidth consumed)
3. DFS (up/down/bandwidth consumed)
4. DFS extras (# of files in queue for sync, file currently being transferred, etc)
This company has some decent tech knowledge(1), so if I could give them a tool that would return this info, it would make them more autonomous (a good thing) and give more confidence in the replication scheme (a very good thing).
(1)Earlier today the boss used the phrase "I think it's a DNS issue" and was right. I was floored.
I'm trying to put together some kind of monitoring package, something that could give useful information about the health/status of the VPN/DFS links. Things I would like to know:
1. Internet (up/down/bandwidth consumed)
2. VPN (up/down/bandwidth consumed)
3. DFS (up/down/bandwidth consumed)
4. DFS extras (# of files in queue for sync, file currently being transferred, etc)
This company has some decent tech knowledge(1), so if I could give them a tool that would return this info, it would make them more autonomous (a good thing) and give more confidence in the replication scheme (a very good thing).
(1)Earlier today the boss used the phrase "I think it's a DNS issue" and was right. I was floored.