|
|
Post by Makzimia on Oct 15, 2004 13:40:15 GMT
Please note, for those that rely on gamespy still for listing of the server, and or lost us in the shuffle from 1.62 to 1.64. I was listed as [1] Makzimia's Bane CEP, seems to have lost a LOT of people. So, I have taken the 1 off the front and gone back to Makzimia's Bane CEP.
And remember direct IP is 70.179.11.23:5123 now, thanks to the fine folks at cox. That is on the news fader, and was posted before, but some seem to have missed it.
Sorry,
Makz.
|
|
|
|
Post by Kliest on Oct 15, 2004 14:27:03 GMT
I think COX's new router is blocking IP's cause IoF is gone for me. If people are missing, isnt it possible they are having similar issues, but they are not vocal on the forums.
I will check to see if IoF ever returns to me, but I am moving along.
C'ya.
Kliest
|
|
|
|
Post by Silentus on Oct 15, 2004 15:07:40 GMT
Is it dead when you try to direct connect to that IP Kliest? I assume this started hapening with the router change, but just to make sure that it is not on your ISPs side, you might want to run a traceroute to make sure that you are getting out . There is a chance that it is your ISP or even local software on your system that doesnt like the New Address.
From a Windows 2k or XP box just run tracert 70.179.11.23 Note: you should just be looking for indications that you are no longer inside your local ISPs system before you get timeouts.
|
|
|
|
Post by Makzimia on Oct 15, 2004 15:08:36 GMT
Perhaps your ISP has had an issue with Cox, but, I can assure you, we are here, and listed definitely on PW Story, I have had that confirmed from several sources now. Sorry you can't see us. And note, tracert may not find my IP due to ICMP blocking, I am not sure. But since most find us, well.
Makz.
|
|
|
|
Post by Silentus on Oct 15, 2004 15:30:41 GMT
It doesnt get all the way there makz, but it does get to a bunch of cox's sites before timeing out - the last valid hop I got was to Edit removed DNS server for a reason  |
|
|
|
Post by Makzimia on Oct 15, 2004 15:50:23 GMT
And that address silentus, is their server for DNS  so, as you see, we are here, as you know  |
|
|
|
Post by Kliest on Oct 16, 2004 16:01:40 GMT
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
|
|
|
|
Post by Makzimia on Oct 16, 2004 16:51:59 GMT
Tell you one thing that is 100% certain Kliest, you are not getting outside your own network, note both 65 addresses after your internal address. Are you on a router of your own? it's really weird you can get on any other servers at all, if that is as far as your trace got. Totally out of ideas, but I do know one thing that is 100% certain, it's not my end |
|
|
|
Post by ride on Oct 16, 2004 19:26:51 GMT
kliest, traceroute didn't "know" it was a cox address, dns told it that information, nothing special about that. do you have any firewall software running on the system in question or on any wierd router/firewall config's on your home network? (like did you install XP service pack 2? the firewall that comes with that could be causing issues) it could be that your *sending* just fine, but your machine is refusing the connection back from the server, due to an over aggressive firewall setting on your host... obviously you *can* get out onto the 'net in some fashion (your making posts).... so.... can you access other NWN servers? I am assuming so since you said you'd be "moving on" but have you tried it actually? and did you let that trace finish running or did you stop it as soon as it started timing out? cause *alot* of routers and hosts nowadays do not accept ICMP (what traceroute and ping are) due to virus and cracker activities. it could have kept going and told you more information. (tho I can trace and ping fine to those 65.x.x.x address from my end...) I am curious as to what IP your timing out on? do you get an IP address or just "timeout"? try running this and see what you get: (dang let me remember the windows command line now.... gah!) tracert -d 70.179.11.23 (the -d will stop it from making DNS requests and just do the trace by IP address only) and *make sure* you didn't use "," instead of "." in the IP, I do that myself sometimes even.... sorry for the 20 questions, just trying to help and that's all for now... I am still thinking and poking around on this a little, if I come up with anything else I will post it here... |
|
|
|
Post by Kliest on Oct 16, 2004 23:11:33 GMT
Ok, letting it run while I type.
I have been playing on other servers. I had a number of servers in my favorites, and they are all still there.
I did install the sp2 weeks ago. Had no issues. Only when the Cox router issue and IP address for IoF changed did I have problems.
Not much of a xp firewall expert but it did ask me about NWN and I told it to allow that program to go thru firewall. Any idea on what config I would need to change? I installed the default. I poked around in there but did not see anything interesting.
Or, what do I say to my ISP that may allow them to figure this out?
I appreciate all the help from everyone.
Well. Got to trace complete with exactly the same results.
Anymore ideas? Lent (my cleric) is waiting and nearly Epic.......
Thanks
Kliest
|
|
|
|
Post by ride on Oct 17, 2004 6:57:44 GMT
can you trace to this address Kliest? what about pinging it? 68.6.9.249 (should be 1 hop away from IoF) let me know what you get for output in this thread. and isn't there another windows command line util. like pathping or something like that?? silentus? I think that might give us more info. (dropped packets and the like) |
|
|
|
Post by Kliest on Oct 17, 2004 15:42:50 GMT
No problem pinging that one...
|
|
|
|
Post by Makzimia on Oct 17, 2004 16:17:48 GMT
Good Kliest, well I suggest a: try looking for Makzimia's Bane CEP again within PW Story list on game spy, and b: retry to get onto server via 70.179.11.23:5123, because unless your ISP has ME blocked, you should be able to get on, also, check to see what message you get when you try that address.
Makz.
|
|
|
|
Post by Silentus on Oct 18, 2004 14:00:59 GMT
Ride- Yeah, there is pathping, but I dont think the data it sends back is going to be too helpfull here. Basically it willl probably simply fail 100% at the same locations. He can certainly try it. (syntax pathping 70.179.11.23 -p 10 - takes about 30 sec to finish getting its stats as it will send 10 pings to each host along the path and returns a report of how each site responds.) Kliest - Had you just upgraded to XP SP2 at about the same time? That animal can mess people up pretty bad (though I havnt seen it cause problems to IoF). Try this: (at least temporarily) 1. Start / Settings / Control Panel / Network Connections 2. Right click your connection and choose properties 3. Advanced tab / Settings button 4. Change windows firewall to Off - see what this does. If it fixes it, I'd have to check and see what to do to get around it permanently. Your best bet in that scenario is to get a hardware router (~$30) and forget windows lame built-in thing. A hardware firewall is always better anyway and they really arent that hard to configure. Plus youre then well on your way to a proper home network! Some cable modems MIGHT have a hardware firewall built-in, it would make sence, though mine does not. EDIT : fixed IP |
|
|
|
Post by Kliest on Oct 18, 2004 15:44:58 GMT
Hey All,
Not at home today, so will try pathping later.
I did look at Gamespy last night but still no IoF
I did upgrade xp sp2, but it was a couple weeks before problem. I played on IoF up to the day the router changed.
Wednesday I will try to go back to my ISP with questions, and a more general request for them to try and figure this out.
If I can Ping 68.6.9.249, I know that I am getting close to the COX IP for the IoF Router....but still can not Ping IoF
Either my ISP or Cox is not allowing me access.
My ISP says they do not have any IP blocked.
Would it be worth it to me to call Cox?
The problem appears to not be on the IoF end, or my end, but somewhere in the middle of cyberspace where Cox and Rye Telephone meet.
I dont want to have the two ISP's talk so much, cause Cox will try to boss them around, and Rye is small town Colorado, and we carry guns. If there could be a shootout over the web, it would happen.
The never ending saga. Well its only been a week so far but it seems neverending...
Kliest
|
|
so, as you see, we are here, as you know 
"There are only three sports--mountain climbing, bullfighting, and motor racing--all the rest being games." Ernest Hemingway 