<div>
<div><p style="color: #a0a0a0;">On Sunday, 16 January 2011 at 7:43 AM, John Durham wrote:</p>
<blockquote type="cite" style="border-left-style:solid;border-width:1px;margin-left:0px;padding-left:10px;">
<span><div><div>May I add to the previous message that when accessed in house the server <br>responds as it should (as far as I can tell), but somehow all that and a <br>check of the cable connection is not enough to get it on line.</div></div></span></blockquote><div><br></div><div>Are you able to tell us which steps that you used to verify that it was working locally? That is, did you open up a web browser on localhost </div><div><br></div><div>This seems almost to be a DNS issue. Here are some things to check:</div><div><br></div><div><div> - Is your router forwarding packets to the correct local IP address?</div><div><br></div><div>When you refreshed your server, you may have deleted something that asked for a static IP address. Your router may be forwarding packets to the right address, but your server has been given another address via DCHP.</div></div><div><br></div><div> - Can your server reach the Internet?</div><div><br></div><div>If not, then the Internet can't reach you..</div><div><br></div><div> - Is the global DNS system sending requests to your server?</div><div><br></div><div>It could be the case that DNS is sending things to the wrong place. I don't think this is likely- as you've made local changes. However, can you ping your router's IP address? (Also, you'll want to log into the router's web admin page and enable responses to ping requests)</div><div><br></div><div>There are a few other things that could have gone wrong. In the meantime, you should consider using a remote hosting provider, uploading the HTML files and change the DNS records. That will give you some time while you're fixing your issues.</div><div><br></div><div>Tim</div><div> @timClicks</div><div> http://timmcnamara.co.nz/</div>
</div>
</div>