I have a website I need to be able to access. It is one that we use
frequently. I could access it a couple weeks back but recently it
does not respond from inside the BorderManager.

I can ping any other site I have tried as well as complete a TraceRt.I have unloaded IPFLT and tried this - I have added the Any group both

in and out with no luck. If I hook a laptop up between the BManager
and the Internet Router I can tracert fine as well as access the site.


I have cleared the proxy (Proxy -cc), checked my Resolv.cfg, tried
access by both IP and DNS and it always fails. The Tracert is alwaysthe same at Step 9, 10, and 11 below. The recursive calls to the .84and .85 have me stumped.

Again - this works between the Bmanager and Internet router as well as

from inside the router. I can not ping or Tracert from the Bmanager
to this site from the Bmanager console either. All other sites seem
fine. Tried reset Internet Router just in case as well as flushed the

Internal Routers. Reset Router on the Bmanager and I have restarted
the BManager as well.

Anyone have an idea what I may be missing or where this route is
stuck?

Thanks,

Scott

Tracing route to www.migsirs.com [198.65.246.24]

over a maximum of 30 hops:



1 2 ms 1 ms 1 ms dac_router.xxxxxxxxxxx.org
[xxx.xx.145.1]

2 1 ms 1 ms 1 ms bmanager [xxx.xx.144.11]

3 4 ms 3 ms 3 ms xxx.xx.145.241

4 6 ms 5 ms 5 ms 206.166.121.141

5 5 ms 5 ms 5 ms jrtc0-fe1.chicago.lincon.net
[206.166.119.10]

6 5 ms 6 ms 5 ms ge0-1-3.sob10.chicago.lincon.net
[206.166.2.57]

7 6 ms 5 ms 5 ms 206.166.9.117

8 22 ms 5 ms 5 ms sl-gw33-chi-4-3.sprintlink.net
[144.223.60.209]

9 5 ms 6 ms 7 ms sl-bb22-chi-4-0.sprintlink.net
[144.232.26.21]

10 7 ms 7 ms 7 ms sl-st20-chi-14-1.sprintlink.net
[144.232.20.84]

11 6 ms 7 ms 6 ms sl-bb22-chi-6-3.sprintlink.net
[144.232.20.85]

12 16 ms 7 ms 7 ms sl-st20-chi-14-1.sprintlink.net
[144.232.20.84]

13 7 ms 7 ms 7 ms sl-bb22-chi-6-3.sprintlink.net
[144.232.20.85]

14 7 ms 7 ms 7 ms sl-st20-chi-14-1.sprintlink.net
[144.232.20.84]

15 8 ms 24 ms 15 ms sl-bb22-chi-6-3.sprintlink.net
[144.232.20.85]

16 9 ms 7 ms 7 ms sl-st20-chi-14-1.sprintlink.net
[144.232.20.84]

17 9 ms 7 ms 7 ms sl-bb22-chi-6-3.sprintlink.net
[144.232.20.85]

18 9 ms 8 ms 8 ms sl-st20-chi-14-1.sprintlink.net
[144.232.20.84]

19 8 ms 9 ms 8 ms sl-bb22-chi-6-3.sprintlink.net
[144.232.20.85]

20 9 ms 9 ms 9 ms sl-st20-chi-14-1.sprintlink.net
[144.232.20.84]

21 17 ms 9 ms 9 ms sl-bb22-chi-6-3.sprintlink.net
[144.232.20.85]

22 10 ms 9 ms 10 ms sl-st20-chi-14-1.sprintlink.net
[144.232.20.84]

23 10 ms 9 ms 9 ms sl-bb22-chi-6-3.sprintlink.net
[144.232.20.85]

24 9 ms 9 ms 9 ms sl-st20-chi-14-1.sprintlink.net
[144.232.20.84]

25 9 ms 9 ms 9 ms sl-bb22-chi-6-3.sprintlink.net
[144.232.20.85]

26 10 ms 11 ms 10 ms sl-st20-chi-14-1.sprintlink.net
[144.232.20.84]

27 11 ms 10 ms 11 ms sl-bb22-chi-6-3.sprintlink.net
[144.232.20.85]

28 11 ms 21 ms 11 ms sl-st20-chi-14-1.sprintlink.net
[144.232.20.84]

29 11 ms 11 ms 11 ms sl-bb22-chi-6-3.sprintlink.net
[144.232.20.85]

30 12 ms 11 ms 11 ms sl-st20-chi-14-1.sprintlink.net
[144.232.20.84]



Trace complete.