Demand Call Requested By {Local IP Address}
Background:
Netopia 4686XL Router used as the main router/Gateway for my office in Chicago.
Similar DSL based Netopia router used for my Wisconsin office.
In addition to the routers providing basic access for both offices to the Internet, I have established a router to router PPTP VPN between the two routers for Office to Office connectivity.
There are other PPTP VPN accounts in the Chicago Office Router (PC to router types) for several remote access users that need this type of access from time to time, including seperate accounts created for the users in the Wisconsin office.
Basic Problem:
This morning, no one in the Wisconsin office can access anything outside the office: not only The Chicago office, but the Internet or anything (Yes, I'm going to call the ISP for the WI office, but I wanted to get this in incase the answer is "Yes, their service is UP"). My Router is trying to connect to the Wi. router but cannot.
Other VPN clients NOT from the Wisconsin office are able to do a PPTP VPN from their computers to my Office router here in Chicago without a problem.
There is an additional strange message in the WAN logs for my Chicago router: "Demand Call Requested By {Local IP Address}". The local address is various LAN addresses from my Chicago network (10.10.70.0). This message keeps cycling over and over with a different address each time.
I did make some changes to the router config (added a static route to an internal subnet I have setup here in Chicago for testing purposes) but that was over a week ago -This issue just popped up today!?
...Help!
Netopia 4686XL Router used as the main router/Gateway for my office in Chicago.
Similar DSL based Netopia router used for my Wisconsin office.
In addition to the routers providing basic access for both offices to the Internet, I have established a router to router PPTP VPN between the two routers for Office to Office connectivity.
There are other PPTP VPN accounts in the Chicago Office Router (PC to router types) for several remote access users that need this type of access from time to time, including seperate accounts created for the users in the Wisconsin office.
Basic Problem:
This morning, no one in the Wisconsin office can access anything outside the office: not only The Chicago office, but the Internet or anything (Yes, I'm going to call the ISP for the WI office, but I wanted to get this in incase the answer is "Yes, their service is UP"). My Router is trying to connect to the Wi. router but cannot.
Other VPN clients NOT from the Wisconsin office are able to do a PPTP VPN from their computers to my Office router here in Chicago without a problem.
There is an additional strange message in the WAN logs for my Chicago router: "Demand Call Requested By {Local IP Address}". The local address is various LAN addresses from my Chicago network (10.10.70.0). This message keeps cycling over and over with a different address each time.
I did make some changes to the router config (added a static route to an internal subnet I have setup here in Chicago for testing purposes) but that was over a week ago -This issue just popped up today!?
...Help!
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
The logical assumption is that Chicago users needed to acces the Wisconsin data site. An access attempt, presumably seen as 'interesting traffic' by the Chicago router, forces a vpn connection. If the VPN cannot be established, it will timeout.
I don't want/need your points - that is not what I am here for. In reality, my comment reflects the operation of demand-dial routing so I am not sure what could be incorrect about it. That said, if the problem is fixed then it doesn't really matter. Delete it if you want to.
keith
keith
ASKER
The main connectivity problem with Wisconsin is the ISP. Wisconsin is back on line. So, what we are left with for this question is the message "Demand Call Requested By {Local IP Address}".
At least I know now that this message, and the Wisconsin issue are unrelated!