Makzimia's Bane CEP as listing.

[ride]

you'll *never* be able to actually ping or traceroute to IoF, makz has ICMP disabled.... *mutters about the old days when the 'net was not a warzone*

but you *could* get to the "one hop away" address..... hmmm
freaking weird.

makz... can we set ya up with a dyn DNS thing then? then your IP can change to your ISP's hearts content and we'd all be able to just use a common hostname for IoF.

and Kliest... when you call your ISP (which is what I would do at this point) tell them this: you *can* get to *any* other sites without a problem but for some reason you cannot access this one certain address (and it is very important that you do, tell em it's your work's VPN connection or something lol). ask them if they can trace from *your* gateway to the IP in question, make sure you tell them that the end IP doesn't accept ICMP as they may see no response and just figure that the address is down and give up (we all know how much tech support ppl hate to do actual tech support). If you can't trace to it, then they should not be able to as well. email them your tracert output if you have to.

oh a whim I inputed the IP for IoF into the "bad IP addresses" list(s) (spam blacklists, etc...) and I got no hits, so it is not that.... unless your IP, kliest, is in there and Cox (or someone else in between) is blocking that IP.... dang could be so many things.... keep trying tho.... I really kinda doubt it is you as it seems to be an issue with an intermediary system. (which are of course, hard to nail down and get resolved)

[Silentus]

Kliest said:

not sure what this means.

it appears it knew it was a cox connection
Tracing route to ip70-179-11-23.sd.sd.cox.net [70.179.11.23] over a max of 30 hops

1. 1ms 192.168.254.254
2. 8ms 65.121.62.5
3. 6ms 65.121.60.130
4. * Request timed out.


I called my ISP the day after the router changed and the problems started, and they said they to not block any addresses, did some checking and then thought is was on the Cox side.

Any ideas for next steps?

Kliest

Based on this, it looks like either your ISP (or whoever is 1 hop up the line from 65.121.60.130) is blocking Makz' IP address. It is never even getting to Cox for them to route it. If you want more ammo before talking with ISPs you could do this as well:
Can you ping the following:
1a. 70.179.11.1
1b. 70.179.11.4
2a. 70.179.10.1
2b. 70.179.10.4
3a. 70.178.10.1
3b. 70.178.10.2

What that tells you is how big of an area is being blocked.
A. 1 (a or b) 2 (a or b) & 3 (a or b) work: They are probably specifcally blocking Makz IP address.
B. 1 (a&b) fail: Then they are probably blocking that whole 70.179.11.x subnet
C. 1 (a&b) & 2 (a&b) fail: Then they are likely blocking the entire 70.179.x.x subnet - that starts becoming a significant blocked range.
D. All 6 fail: They are likely blocking the entire 70.x.x.x trunk. Thats very large indeed.

Note that usually x.x.x.1 is usually used for routers or switches and the likes and generally stay up all the time. Other address may be pcs or servers or anything so they could may be more likely to go down depending on when you test. All of these were verified live at 1pm CST today. I supplied 2 live addresses for each just to try to cover for equipment that may not be up when you do the test.

[Kliest]

Argh..
Of course the whole trunk for 70.xx down is blocked to me.

My ISP says they do not have any problems pinging these. So, somewhere I have that whole turnk blocked?

I do not see a setting in the windows firewall to do this.

Any next steps?

THanks
Kliest

[ride]

i really doubt your going to find anything in the winblows firewall that's doing it.

hmmm weird....

ok some more ideas as they coalesce in my head....

can you run the ping(s)/traceroute(s) *from your router*?

if you can... what do you get from there?

can you look up (on your router) the gateway for you to enter your ISP's network? (should be 65.121.62.5)

this is so you can call your ISP and tell them... look, you login to this system and try to get to the address(es) in question from there, cause I sure can't! sure they may be able to ping those address(es) from whatever system they are sitting at in the tech-support cube, but they *could be using a different route*. Whatever they see, you wont nesessarily see.

As far as I can tell tho Kliest, *IT IS NOT YOU* so stop thinking you can do something on your end to fix it, cause most likely you cannot, and we'll have to work together to find the right words to convince your dang ISP to actually look at this issue cause it sounds to me like they are blowing you off.


*longs for the days when the 'net was a free exchange of information and not a marketing/attack/political tool*