09-10-2006 07:35 PM - edited 03-03-2019 01:57 PM
I got something here and need your expert :)
We got a satellite link to our HQ where our internet connection is. I believe the setup here is where our proxy in branch office synchronize with the upstream proxy server in HQ often. I have been noticing this error message on our proxy server here in the branch office.
"MESSAGE : The Web Proxy service detected that the upstream proxy '172.18.1.18' is not available. For more information about this event, see ISA Server Help."
Go through the web on EventID and found out that this problem is caused by network bridging. I have to verify that all NIC's in the scenario are all on the separate subnets.
Anyway, I don?t have full access to the satellite router here but go as far as the user exec mode ): Do a "show ip route" and got this. I'm a bit suspicious with the routing. Would appreciate if you could go through the routing here and let me know of any problem that could have link to the error message that we are receiving from our proxy server. The ip address of the server here in branch office is 192.168.0.13 and the HQ one is 172.18.1.18
Codes: C - connected, S - static, R - RIP, M - mobile, B - BGP
D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
E1 - OSPF external type 1, E2 - OSPF external type 2
i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
ia - IS-IS inter area, * - candidate default, U - per-user static route
o - ODR, P - periodic downloaded static route
Gateway of last resort is 172.19.0.1 to network 0.0.0.0
R 192.168.10.0/24 [120/2] via 192.168.0.6, 00:00:07, FastEthernet0/0
S 192.168.40.0/24 [1/0] via 192.168.0.6
172.19.0.0/16 is variably subnetted, 2 subnets, 2 masks
C 172.19.0.1/32 is directly connected, Multilink2001100114
C 172.19.0.0/24 is directly connected, Multilink2001100114
R 172.18.0.0/16 [120/1] via 172.19.0.1, 00:00:01, Multilink2001100114
R 10.0.0.0/8 [120/1] via 192.168.0.6, 00:00:07, FastEthernet0/0
C 192.168.0.0/24 is directly connected, FastEthernet0/0
R 192.168.50.0/24 [120/1] via 192.168.0.6, 00:00:07, FastEthernet0/0
S* 0.0.0.0/0 [1/0] via 172.19.0.1
Hope you will help
09-10-2006 08:12 PM
Hie Usaia,
From the output of sh ip route it is seen that from your network your main proxy is reachable thorugh 172.19.0.1
You can check following few things
1. Can you ping your main proxy server from local proxy server.
2. If for some reason ping is disabled on that, can you ping any machine in the subnet of your main proxy server.
If these things are working apparantly there is no issue with communication at network level. Then we may need to check some other things
09-10-2006 08:43 PM
Can ping across. Im not too sure whether network 172.18.0.0 should be included in the RIP configuration at the remote branch end. Is that an issue ? From what I get on the event id and from researching through the web about this particular event id, they say that this is due to the network being bridged.
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide