Quote:
Originally posted by Megabot:
Hmmm have you thinking on to move the IW to a BIG ISP Z? Then maby some of us dont get this damn DNS error 90% of the time we try to log on to IW? I had this problem now for about 6 months and still have problems and dont tell me to call my isp they dont find any problems so it have to be in your end of the line, and i have not any problems with other forums or webpages only IW!! 
|
Mega, it *IS* on your end. It *IS* your ISP`s problem (or maybe, but probably not, your broswer`s).
And no, don`t call them. ISPs will NEVER find any problems, always say it is someone elses problem, and would (hopefully) never be called by any sane person. 
If it is DNS, the following *will* fix it:
Go into DOS Prompt (Start -> Run -> Command )
Type: CD C:\WINDOWS
Type: Edit hosts.sam
Add the line:
24.129.133.61 www.ironworksforum.com
To the bottom of the file; save and exit;
Type: Edit lmhosts.sam
Add the line:
www.ironworksforum.com 24.129.133.61
To the bottom of the file; save, exit;
Back in DOS type: ren hosts.sam hosts
ren lmhosts.sam lmhosts
If at either of the "Edit" stages it says "Bad command or file name", simply type the line again without the .sam ; and leave out the relevant "ren" step.
EDIT: Tracer route of www.ironworksforum.com :
Tracing route to ironworksforum.com [24.129.133.61]
over a maximum of 30 hops:
1 <1 ms <1 ms <1 ms spirit.mshome.net [192.168.0.1]
2 211 ms 98 ms 68 ms 172.31.17.152
3 69 ms 38 ms 109 ms 172.31.52.24
4 58 ms 39 ms 39 ms CPE-61-9-207-29.nsw.bigpond.net.au [61.9.207.29]
5 108 ms 39 ms 49 ms CPE-61-9-193-8.nsw.bigpond.net.au [61.9.193.8]
6 38 ms 39 ms 39 ms GigabitEthernet3-1.pit2.Sydney.telstra.net [139.
130.94.97]
7 48 ms 39 ms 39 ms GigabitEthernet1-2.pic1.Sydney.telstra.net [203.
50.12.29]
8 38 ms 39 ms 39 ms GigabitEthernet11-1.ken-core4.Sydney.telstra.net
[203.50.12.117]
9 77 ms 39 ms 39 ms Pos2-0.pad-core4.Sydney.telstra.net [203.50.6.22
]
10 57 ms 39 ms 39 ms GigabitEthernet0-1.syd-core01.Sydney.net.reach.c
om [203.50.13.246]
11 227 ms 229 ms 429 ms 202.84.143.41
12 227 ms 229 ms 229 ms 134.159.63.62
13 227 ms 229 ms 229 ms so-5-0-0.gar1.SanJose1.level3.net [209.244.3.137
]
14 227 ms 229 ms 228 ms so-7-0-0.mp1.SanJose1.Level3.net [64.159.1.73]
15 316 ms 319 ms 319 ms so-3-0-0.mp2.Atlanta1.Level3.net [64.159.1.46]
16 316 ms 319 ms 319 ms gigabitethernet11-1.hsipaccess2.Atlanta1.Level3.
net [64.159.3.10]
17 316 ms 319 ms 319 ms POS11-0.hsipaccess2.Atlanta2.Level3.net [209.244
.15.122]
18 266 ms 269 ms 269 ms pop2-atm-P0-2.atdn.net [66.185.138.33]
19 265 ms 269 ms 269 ms bb2-atm-P0-1.atdn.net [66.185.147.213]
20 285 ms 289 ms 289 ms bb1-tby-P7-0.atdn.net [66.185.152.244]
21 285 ms 289 ms 279 ms pop2-tby-P0-0.atdn.net [66.185.136.177]
22 283 ms 289 ms 289 ms rr-tampa.atdn.net [66.185.136.186]
23 284 ms 289 ms 289 ms 65327hfc89.tampabay.rr.com [65.32.7.89]
24 283 ms 289 ms 289 ms 4700-atm.tampabay.rr.com [24.92.0.253]
25 * * * Request timed out.
26 290 ms 289 ms 289 ms rrcs-se-24-129-133-61.biz.rr.com [24.129.133.61]
Trace complete.
[ 10-19-2002, 09:28 PM: Message edited by: LennonCook ]