Connection problems to I-Mod Productions? go here

ISP and the hell

Some of you encountered problems to access the I-mod sites in the past months.

We contacted our Hoster and had to change our IP's, cause the old seem to be blocked by one or more providers, but now it seems we are back for most of you.

If you encounter problems, we can work it out and make I-Mod accessable for you with your help, please go to the last page and help us tracing it!

Sry for the circumstances.

See you on I-Mod!

 

-Stefan

46,125 views 76 replies
Reply #1 Top

VERY simple mine doesn't get out of the local ISP servers switching "locks";

TO 87.118.120.209

stepping and stuck on first node 192.168.2.1 (which is assigned by either Montreal or Toronto redirections)

WHOIS lookup?

Dynamic allocation, daily or on every Vista booting resets...

67.68.253.136 (currently detected IP)

HOSTED by... bas4-montrealak-1128594824.dsl.bell.ca

NameServer: TOROON63NSZP05.SRVR.BELL.CA
NameServer: TOROONDCNSZS05.SRVR.BELL.CA

Tomorrow and ever after, Bell Sympatico will automatically scramble that stuff - as usual. They claimed your hosting server is somehow flawed, too.

I will switch off that Speedstream 4200 modem as soon as i exit my browser and this site, btw... just to make sure that IP is no longer active. So hackers, beware even a fraction of a second won't ping me fast enough.

Reply #2 Top

87.118.120.219   not 87.118.120.209, did you made a typo?

Reply #3 Top

Yep sorry, typo. With these numbers, one cannot even mistype a single digit; falsifying any further attempts at a solid diagnostic.  :\

Reply #4 Top

Mine says...

Tracing route to i-mod-productions.com [87.118.120.219] over a maximum of 30 hops:

1    2 ms    6 ms    4 ms    192.168.1.1

everything after this is request timed out.

Reply #5 Top

Local LAN - as anyone running Vista on DSL.

Reply #6 Top

please give me more detailed information when it stops (what was the last carrier) not only the IP.

I need more logs guys.

Reply #7 Top

this is as far as mine gets:

 1    <1 ms    <1 ms    <1 ms  dslrouter [192.168.1.1]
 2    23 ms    23 ms    23 ms  10.32.163.1
 3     *        *        *     Request timed out.

Reply #8 Top

I don't quite understand Stefan, did I miss something in my post?  I just tried again with the same results, everything just says

1    2 ms    6 ms    4 ms    192.168.1.1

(2-30)    *    *    *    Request timed out

I'm on Verizon FIOS, using an Actiontec router, with portforwarding to my machine only, out of Annapolis, Maryland.  I also tried using Firefox but no luck with that either.  Not sure if any of that helps.

Reply #9 Top

by posting the tracert here, nothing happens. by stefan submitting them to his host, things may get fixed upon further investigation by the host.

Reply #10 Top

I understood that part DSep, but was confused when Stefan said he needed more detailed information and was wondering if I had left out any.  Thx for trying to clarify though.

Reply #11 Top

Quoting Mr, reply 8
I don't quite understand Stefan, did I miss something in my post?  I just tried again with the same results, everything just says

1    2 ms    6 ms    4 ms    192.168.1.1

(2-30)    *    *    *    Request timed out

I'm on Verizon FIOS, using an Actiontec router, with portforwarding to my machine only, out of Annapolis, Maryland.  I also tried using Firefox but no luck with that either.  Not sure if any of that helps.

 

I'm having the same problem Mr. Nice Guy.  And guess what?  I'm on Verizon FiOS too in western Washington, east of Seattle in Redmond.  Anyway, it just keeps hopping with a maximum of 30 hops and the only one it show anything other than request timed out is the very first one.

For more info I'm running on Vista 64 bit sp1.  e8400 CPU, EVGA 280 and about 4t of storage space.  Using on-board sound of a P5E motherboard with BIOS 0903. Oh, and 8gig of PC1066.

 

It does give me the IP for i-mod (87.118.120.219) and the only other it shows is mine (myrouter.home) with 1ms then everything else is timed out with no listing of names or anything else helpful.  Sorry.

Reply #12 Top

@mr nice guy, sorry I was hoping there was more information given by your tracert command, this result doesn't seem to be helpful as no other carrier blocks it, just your own router...

anyway, I will pull together all your posts and send it right to the hoster.

 

PS: are all of you using vista?

Reply #13 Top

I got a response from our hoster, the tracerts get stuck far outside their network. They suppose there is a problem in the route delivery between individual carriers.

I need your help again, this time please tracert these IP's and give me your results

193.22.254.100
95.169.160.33
87.118.122.38
87.118.120.128
62.141.52.1

Our hoster tries to focuse the problem.

thanks in advance,

Stefan
Reply #14 Top

I'm using Windows XP Professional.  So strange that it's getting stuck at my router but not having any other internet issues.  Computers are confusing. :)

But like Stroxuss points out, us FIOS guys are having the same problem so far.  Their tech support has been surprisingly helpful the couple times I've had to call but I wonder how they would respond to this one lol.  Doesn't hurt to try I suppose if you think it might be beneficial.

Reply #15 Top

yeah this situation is really confusing, its a strange feeling when many people outside germany can't access to your site and you can't do something directly.

So far, my hoster needs the tracert of this test IP's, so if you could help me with that I would be really thankful =)

-Stefan

Reply #16 Top
193.22.254.100;
same stucked 30 step delays (...at LAN 192.168.2.1)
95.169.160.33;
(idem)
87.118.122.38;
(idem)
87.118.120.128;
(idem)
62.141.52.1
(idem)


Hosts file corruption in the usual system32/drivers/etc folder, maybe?

OR routing flaws caused by "server side" provided by any of our ISP?

M$ updated Vista with a specific KB a few weeks ago which certainly triggered it back online for awhile...
Reply #17 Top

Tracing route to sarah.ef-ix.de [193.22.254.100] over a maximum of 30 hops:

  1     3 ms     4 ms     2 ms  192.168.1.1
  2     5 ms     7 ms     7 ms  173.64.104.1
  3     9 ms     9 ms     7 ms  G10-0-3-439.BLTMMD-LCR-04.verizon-gni.net [130.81.109.20]
  4    11 ms    12 ms    12 ms  so-2-0-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.28.82]
  5    79 ms    12 ms    37 ms  0.so-6-0-0.XL2.PHL6.ALTER.NET [152.63.3.81]
  6    13 ms    12 ms    14 ms  0.so-3-0-0.IL4.DCA6.ALTER.NET [152.63.41.66]
  7    12 ms    12 ms    15 ms  so-1-0-0.IL2.DCA4.ALTER.NET [146.188.15.101]
  8   101 ms   102 ms   102 ms  ge-0-1-0.XT1.FFT1.ALTER.NET [146.188.14.137]
  9    98 ms    97 ms    99 ms  so-0-0-0.CR2.FFT1.ALTER.NET [146.188.15.194]
 10    98 ms    99 ms    99 ms  POS1-0.GW2.FFT4.ALTER.NET [149.227.16.38]
 11   102 ms    99 ms    99 ms  ude201961-gw.customer.ALTER.NET [146.188.70.202]

 12    99 ms    97 ms    99 ms  ffm-145-254-16-73.arcor-ip.net [145.254.16.73]
 13   102 ms   102 ms   102 ms  ffm-145-254-1-10.arcor-ip.net [145.254.1.10]
 14   153 ms   154 ms   152 ms  145.253.13.74
 15   113 ms   112 ms   112 ms  95.169.160.42
 16   155 ms   157 ms   157 ms  sarah.ef-ix.de [193.22.254.100]

Trace complete.

Reply #18 Top

Tracing route to 95.169.160.33 over a maximum of 30 hops

  1     2 ms     3 ms     2 ms  192.168.1.1
  2     6 ms     7 ms     4 ms  173.64.104.1
  3     6 ms     7 ms     4 ms  G10-0-3-339.BLTMMD-LCR-03.verizon-gni.net [130.81.107.206]
  4     8 ms     7 ms     9 ms  so-9-2-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net [130.81.28.80]
  5    12 ms     9 ms    10 ms  0.ge-4-2-0.BR2.IAD8.ALTER.NET [152.63.32.141]
  6    11 ms    10 ms    11 ms  204.255.169.202
  7   100 ms    99 ms    99 ms  64.213.33.210
  8   103 ms   102 ms   104 ms  hmb-145-254-18-145.arcor-ip.net [145.254.18.145]

  9   103 ms   104 ms   104 ms  han-145-254-19-161.arcor-ip.net [145.254.19.161]

 10   101 ms   102 ms   104 ms  ffm-145-254-18-81.arcor-ip.net [145.254.18.81]
 11   103 ms   104 ms   104 ms  ffm-145-254-1-14.arcor-ip.net [145.254.1.14]
 12   117 ms   120 ms   119 ms  95.169.160.33

Trace complete.

Reply #19 Top

Tracing route to master.poisonnuke.de [87.118.122.38] over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  192.168.1.1
  2     7 ms     4 ms     4 ms  173.64.104.1
  3     9 ms     7 ms     9 ms  G10-0-3-439.BLTMMD-LCR-04.verizon-gni.net [130.81.109.20]
  4    11 ms    12 ms    12 ms  so-2-0-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.28.82]
  5    12 ms    12 ms     9 ms  0.so-6-0-0.XL2.PHL6.ALTER.NET [152.63.3.81]
  6    13 ms    14 ms    12 ms  0.so-3-0-0.IL4.DCA6.ALTER.NET [152.63.41.66]
  7    14 ms    14 ms    14 ms  so-1-0-0.IL2.DCA4.ALTER.NET [146.188.15.101]
  8   101 ms    99 ms    99 ms  ge-0-1-0.XT1.FFT1.ALTER.NET [146.188.14.137]
  9   100 ms   102 ms   102 ms  so-0-0-0.CR1.FFT1.ALTER.NET [146.188.15.186]
 10    97 ms    97 ms    99 ms  POS0-0-1.GW2.FFT4.ALTER.NET [149.227.17.222]
 11   100 ms    99 ms   102 ms  ude201961-gw.customer.ALTER.NET [146.188.70.202]

 12    97 ms    97 ms    99 ms  ffm-145-254-16-73.arcor-ip.net [145.254.16.73]
 13   102 ms   102 ms   100 ms  ffm-145-254-1-10.arcor-ip.net [145.254.1.10]
 14   154 ms   154 ms   154 ms  145.253.13.74
 15   108 ms   107 ms   109 ms  95.169.160.34
 16   158 ms   157 ms   157 ms  master.poisonnuke.de [87.118.122.38]

Trace complete.

Reply #20 Top

Tracing route to dns.keyweb.de [87.118.120.128] over a maximum of 30 hops:

  1     2 ms     2 ms     2 ms  192.168.1.1
  2     5 ms     4 ms     7 ms  173.64.104.1
  3     7 ms     9 ms     9 ms  G10-0-3-439.BLTMMD-LCR-04.verizon-gni.net [130.81.109.20]
  4    11 ms    12 ms    10 ms  so-2-0-0-0.PHIL-BB-RTR2.verizon-gni.net [130.81.28.82]
  5    10 ms    12 ms     9 ms  0.so-6-0-0.XL2.PHL6.ALTER.NET [152.63.3.81]
  6    14 ms    13 ms    14 ms  0.so-3-0-0.IL4.DCA6.ALTER.NET [152.63.41.66]
  7    12 ms    14 ms    15 ms  so-1-0-0.IL2.DCA4.ALTER.NET [146.188.15.101]
  8   101 ms   102 ms    99 ms  ge-0-1-0.XT1.FFT1.ALTER.NET [146.188.14.137]
  9    98 ms    99 ms    99 ms  so-0-0-0.CR2.FFT1.ALTER.NET [146.188.15.194]
 10    97 ms    97 ms    99 ms  POS1-0.GW2.FFT4.ALTER.NET [149.227.16.38]
 11   102 ms   102 ms    99 ms  ude201961-gw.customer.ALTER.NET [146.188.70.202]

 12    99 ms    99 ms    99 ms  ffm-145-254-16-73.arcor-ip.net [145.254.16.73]
 13   101 ms   102 ms    99 ms  ffm-145-254-1-10.arcor-ip.net [145.254.1.10]
 14   153 ms   154 ms   154 ms  145.253.13.74
 15   109 ms   107 ms   109 ms  95.169.160.34
 16   106 ms   110 ms   107 ms  dns.keyweb.de [87.118.120.128]

Trace complete.

Reply #21 Top

Tracing route to h-62.141.52.1.keyweb.de [62.141.52.1] over a maximum of 30 hops:

  1     3 ms     2 ms     2 ms  192.168.1.1
  2     6 ms     4 ms     4 ms  173.64.104.1
  3     6 ms     4 ms     4 ms  G10-0-3-339.BLTMMD-LCR-03.verizon-gni.net [130.81.107.206]
  4     8 ms     9 ms     9 ms  so-9-2-0-0.LCC1-RES-BB-RTR1-RE1.verizon-gni.net[130.81.28.80]
  5    12 ms    12 ms    10 ms  0.so-5-1-0.XT1.DCA5.ALTER.NET [152.63.36.205]
  6    10 ms    12 ms     9 ms  0.so-3-0-0.IL3.DCA6.ALTER.NET [152.63.41.62]
  7    11 ms     9 ms     9 ms  so-1-0-0.IL1.DCA4.ALTER.NET [146.188.15.57]
  8   100 ms    99 ms    99 ms  ge-1-1-0.XT1.FFT1.ALTER.NET [146.188.14.141]
  9    98 ms    97 ms    99 ms  so-0-0-0.CR1.FFT1.ALTER.NET [146.188.15.186]
 10    98 ms    99 ms    99 ms  POS0-0.GW2.FFT4.ALTER.NET [149.227.16.34]
 11    98 ms    99 ms    99 ms  ude201961-gw.customer.ALTER.NET [146.188.70.202]

 12    97 ms    99 ms    99 ms  ffm-145-254-16-177.arcor-ip.net [145.254.16.177]

 13    98 ms    99 ms    99 ms  ffm-145-254-1-14.arcor-ip.net [145.254.1.14]
 14   152 ms   152 ms   154 ms  145.253.13.74
 15   112 ms   112 ms   112 ms  h-62.141.52.1.keyweb.de [62.141.52.1]

Trace complete.

Reply #22 Top

Tracing route to sarah.ef-ix.de [193.22.254.100]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dslrouter [192.168.1.1]
  2    24 ms    23 ms    23 ms  10.32.163.1
  3    23 ms    28 ms    23 ms  130.81.12.173
  4    23 ms    25 ms    23 ms  as0-0.NY325-BB-RTR2.verizon-gni.net [130.81.20.1
78]
  5    31 ms    31 ms    31 ms  0.so-4-3-0.XT2.NYC9.ALTER.NET [152.63.10.5]
  6    31 ms    31 ms    32 ms  0.so-3-0-0.IL4.NYC9.ALTER.NET [152.63.23.177]
  7    32 ms    31 ms    31 ms  so-1-0-0.IL2.NYC12.ALTER.NET [146.188.15.1]
  8   115 ms   115 ms   114 ms  so-0-0-0.XT1.FFT1.ALTER.NET [146.188.14.193]
  9   129 ms   114 ms   114 ms  so-0-0-0.CR2.FFT1.ALTER.NET [146.188.15.194]
 10   114 ms   114 ms   114 ms  POS1-0-1.GW2.FFT4.ALTER.NET [149.227.17.226]
 11   115 ms   114 ms   116 ms  ude201961-gw.customer.ALTER.NET [146.188.70.202]

 12   114 ms   114 ms   113 ms  ffm-145-254-16-177.arcor-ip.net [145.254.16.177]

 13   115 ms   115 ms   114 ms  ffm-145-254-1-14.arcor-ip.net [145.254.1.14]
 14   168 ms   168 ms   169 ms  145.253.13.74
 15   158 ms   157 ms   156 ms  95.169.160.38
 16   197 ms   197 ms   197 ms  sarah.ef-ix.de [193.22.254.100]

Trace complete.

__________________________________________________________-

Tracing route to 95.169.160.33 over a maximum of 30 hops

  1    <1 ms    <1 ms    <1 ms  dslrouter [192.168.1.1]
  2    25 ms    23 ms    23 ms  10.32.163.1
  3    23 ms    23 ms    25 ms  130.81.12.173
  4    23 ms    24 ms    23 ms  as0-0.NY325-BB-RTR2.verizon-gni.net [130.81.20.1
78]
  5    37 ms    33 ms    32 ms  0.so-3-1-0.XT2.NYC8.ALTER.NET [152.63.10.41]
  6    33 ms    33 ms    33 ms  0.so-3-0-0.IL4.NYC9.ALTER.NET [152.63.23.177]
  7    34 ms    32 ms    32 ms  so-1-0-0.IL2.NYC12.ALTER.NET [146.188.15.1]
  8   115 ms   116 ms   115 ms  so-1-0-0.XT1.FFT1.ALTER.NET [146.188.14.234]
  9   115 ms   115 ms   117 ms  so-0-0-0.CR2.FFT1.ALTER.NET [146.188.15.194]
 10   116 ms   115 ms   115 ms  POS1-0.GW2.FFT4.ALTER.NET [149.227.16.38]
 11   117 ms   116 ms   117 ms  ude201961-gw.customer.ALTER.NET [146.188.70.202]

 12   116 ms   116 ms   115 ms  ffm-145-254-16-177.arcor-ip.net [145.254.16.177]

 13   116 ms   116 ms   118 ms  ffm-145-254-1-14.arcor-ip.net [145.254.1.14]
 14   125 ms   124 ms   126 ms  95.169.160.33

Trace complete.

_____________________________________________________

Tracing route to master.poisonnuke.de [87.118.122.38]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dslrouter [192.168.1.1]
  2    24 ms    23 ms    23 ms  10.32.163.1
  3    23 ms    23 ms    25 ms  130.81.12.173
  4    23 ms    25 ms    24 ms  as0-0.NY325-BB-RTR2.verizon-gni.net [130.81.20.
78]
  5    34 ms    33 ms    32 ms  0.so-3-1-0.XT2.NYC8.ALTER.NET [152.63.10.41]
  6    32 ms    33 ms    32 ms  0.so-3-0-0.IL4.NYC9.ALTER.NET [152.63.23.177]
  7    32 ms    34 ms    32 ms  so-1-0-0.IL2.NYC12.ALTER.NET [146.188.15.1]
  8   116 ms   116 ms   115 ms  so-0-0-0.XT2.FFT1.ALTER.NET [146.188.14.197]
  9   116 ms   115 ms   115 ms  so-1-0-0.CR1.FFT1.ALTER.NET [146.188.15.190]
 10   115 ms   116 ms   115 ms  POS0-0.GW2.FFT4.ALTER.NET [149.227.16.34]
 11   116 ms   116 ms   116 ms  ude201961-gw.customer.ALTER.NET [146.188.70.202

 12   115 ms   116 ms   115 ms  ffm-145-254-16-177.arcor-ip.net [145.254.16.177

 13   117 ms   117 ms   116 ms  ffm-145-254-1-14.arcor-ip.net [145.254.1.14]
 14   170 ms   170 ms   173 ms  145.253.13.74
 15   123 ms     *      125 ms  95.169.160.34
 16     *      157 ms   157 ms  master.poisonnuke.de [87.118.122.38]

Trace complete.

_____________________________________________________________________

Tracing route to dns.keyweb.de [87.118.120.128]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dslrouter [192.168.1.1]
  2    24 ms    23 ms    23 ms  10.32.163.1
  3    25 ms    23 ms    23 ms  130.81.12.173
  4    24 ms    23 ms    23 ms  as0-0.NY325-BB-RTR2.verizon-gni.net [130.81.20.1
78]
  5    30 ms    30 ms    30 ms  0.so-4-3-0.XT2.NYC9.ALTER.NET [152.63.10.5]
  6    31 ms    32 ms    31 ms  0.so-3-0-0.IL4.NYC9.ALTER.NET [152.63.23.177]
  7    31 ms    31 ms    31 ms  so-1-0-0.IL2.NYC12.ALTER.NET [146.188.15.1]
  8   115 ms   115 ms   114 ms  so-1-0-0.XT1.FFT1.ALTER.NET [146.188.14.234]
  9   115 ms   115 ms   115 ms  so-0-0-0.CR1.FFT1.ALTER.NET [146.188.15.186]
 10   114 ms   114 ms   115 ms  POS0-0-1.GW2.FFT4.ALTER.NET [149.227.17.222]
 11   115 ms   115 ms   116 ms  ude201961-gw.customer.ALTER.NET [146.188.70.202]

 12   114 ms   117 ms   116 ms  ffm-145-254-16-73.arcor-ip.net [145.254.16.73]
 13   114 ms   115 ms   115 ms  ffm-145-254-1-10.arcor-ip.net [145.254.1.10]
 14   169 ms   168 ms   170 ms  145.253.13.74
 15     *        *        *     Request timed out.
 16   157 ms   156 ms   155 ms  dns.keyweb.de [87.118.120.128]

Trace complete.

____________________________________________________________

Tracing route to h-62.141.52.1.keyweb.de [62.141.52.1]
over a maximum of 30 hops:

  1    <1 ms    <1 ms    <1 ms  dslrouter [192.168.1.1]
  2    24 ms    24 ms    23 ms  10.32.163.1
  3    24 ms    24 ms    23 ms  130.81.12.169
  4    23 ms    23 ms    24 ms  as1-0.NY325-BB-RTR1.verizon-gni.net [130.81.20.1
76]
  5    32 ms    32 ms    32 ms  0.so-3-1-0.XT1.NYC9.ALTER.NET [152.63.10.37]
  6    32 ms    31 ms    31 ms  0.so-3-0-0.IL3.NYC9.ALTER.NET [152.63.23.169]
  7    31 ms    30 ms    30 ms  so-1-0-0.IL1.NYC12.ALTER.NET [146.188.15.5]
  8   115 ms   115 ms   114 ms  ge-0-1-0.XT2.FFT1.ALTER.NET [146.188.14.138]
  9   115 ms   115 ms   115 ms  so-1-0-0.CR2.FFT1.ALTER.NET [146.188.15.198]
 10   114 ms   116 ms   115 ms  POS1-0.GW2.FFT4.ALTER.NET [149.227.16.38]
 11   115 ms   115 ms   116 ms  ude201961-gw.customer.ALTER.NET [146.188.70.202]

 12   114 ms   114 ms   114 ms  ffm-145-254-16-177.arcor-ip.net [145.254.16.177]

 13   115 ms   115 ms   116 ms  ffm-145-254-1-14.arcor-ip.net [145.254.1.14]
 14   169 ms   169 ms   169 ms  145.253.13.74
 15   170 ms   170 ms   172 ms  h-62.141.52.1.keyweb.de [62.141.52.1]

Trace complete.

 

 

Reply #23 Top

The hoster found a possible solution, we needed to change the IP to 87.118.120.11 because some provider may have blocked our IP.

Therefore, the site is currently unavailable for ALL.  Shouldn't take long and after the new routes have been established,

ALL should have access to I-Mod again, instead of China (they block all forums^^)

 

This solution would not have been found without you, so thank you very much!

 

 

 

-Stefan

 

Reply #24 Top

As Stefan said, we - or better I - had to change the IP into a new one, we got temporary from Keyweb, because some ISP named Alter.net seems to block us.

Related to the Availability of our site: Stefan is semi-right; all, who haven't visited us today already should be able to connect to I-Mod, all others have to flush their DNS-Cache (also on their routers).

Reply #25 Top

How soon should connection be possible?