Baffling network problem

JakeJake Alec Baldwin's Chest Hair
edited August 2003 in Science & Tech
Alright, here's the situation, at one of the locations where I have a computer set up, dial-up is the only Internet option. There are two systems at the site; one dials in and shares Internet access via Windows XP's built-in Internet Sharing, and the other system receives that shared Internet access via a wireless connection.

The Internet host system is plugged into a D-Link DI-714 router via a CAT-5, and the client system receives the Internet via a D-Link DWL-AG520 wireless card. The router has DHCP serving disabled, and has been manually assigned the IP of 192.168.2.1 so as not to conflict with the 192.168.0.1 IP that Windows automatically assigns the host system due to the Internet connection sharing.

This setup seems to work perfectly fine for all of my needs at this site, save one: I cannot check the folding stats page at folding.extremeoverclocking.com from the client system, only the host system.

From what I have thus far experienced, this one website is the ONLY website for which this problem exists. Now, I have no idea if this will help anyone solve this mystery, but I have two screenshots for you to look at. This first screenshot shows the info returned from the IPCONFIG command on the host system, as well as the first hop in a TRACERT to www.extremeoverclocking.com and the first hop to folding.extremeoverclocking.com.

Comments

  • JakeJake Alec Baldwin's Chest Hair
    edited August 2003
    And now, the second screenshot shows the info returned from the IPCONFIG command on the client system, as well as the first hop in a TRACERT to www.extremeoverclocking.com and the first hop to folding.extremeoverclocking.com. Note that the TRACERT to www.extremeoverclocking.com begins and passes the host system, but the TRACERT to folding.extremeoverclocking.com dies seemingly before even getting to the host system.
  • JakeJake Alec Baldwin's Chest Hair
    edited August 2003
    So, are there any brilliant network gurus hanging around who can give me any ideas as to what might be going on?

    Or, for that matter, are there any village idiots who can see the forest for the trees and recognize some obvious solution that has, thus far, eluded me?

    Any help is much appreciated.

    Oh, and one last additional piece of info, both systems, the host and the client, have had their DNS resolver caches flushed using IPCONFIG. Sadly, to no avail.
  • EMTEMT Seattle, WA Icrontian
    edited August 2003
    My first piece of advice is to use tracert -d [ip/hostname]... d means don't look up the hostname of each computer on the route and tracert's for me are performed much faster that way.

    Anyway, the problem sounds VERY strange. The tracert should always find the first few things to be the same - especially when you know exactly what those things are.

    So it's still baffling me how this one website won't work. To test a little more you could try the following on CMD:
    telnet folding.extremeoverclocking.com 80 (to see if it really connects at all)
    if it connects you can type:
    GET / HTTP/1.0 [return, return]
    and see if it gives you the HTML.

    Now, I can't access folding.extremeoverclocking.com anywhere at all. I've tried from 4 computers, 3 of which have unique WAN IPs, and nothing at all could see it. One couldn't look it up successfully but every one of them could ping it by IP address.

    While I'm looking into how exactly to access the site (or how 'up' it is) or whatever... [ps: it looks like whatever host that is isn't running any servers at all; are you sure you can access it from your Internet computer right now?]

    What port is the Internet computer on on the router? If it's a regular client port it may be the problem. I think you may have subnet issues with making the router .2.1. Here's what I suggest:
    -keep the router's local IP at .2.1
    -plug your Internet computer into the WAN port of the router (if they can't see each other try a crossover cable)
    -enable the router's DHCP server and set non-Internet comp to DHCP client, or just give it a .2.100 IP address

    What this will do is set up 2 layers of NAT, which is a little redundant but avoids a strange route. 192.168.0.100 -> 192.168.2.1 -> 192.168.0.1 might be weirding it. Or something. I don't know too much about subnets but one time I had someone VPN to a LAN party and his IP was on a different subnet (.1.x vs .0.x) and he couldn't connect to anyone but the computer he was directly connected to.

    Anyway, this message is long enough :) good luck
  • MrBillMrBill Missouri Member
    edited August 2003
    I don't think anyone is getting to that site. Try clearing your cache on the host machine and see if it will still get to it. I'm guessing that it won't.
  • BlackHawkBlackHawk Bible music connoisseur There's no place like 127.0.0.1 Icrontian
    edited August 2003
    The site doesn't work for me either.
  • JakeJake Alec Baldwin's Chest Hair
    edited August 2003
    Alright, problem fixed. Thanks for the ideas, all.

    EMT was on the right track with the subnet theory; turns out, it was even easier than his suggestion. I left the host system plugged in to the first port on the router (as opposed to the WAN port), changed the router's IP to 192.168.0.50, kept the router's DHCP server turned off, left XP's ICS turned on on the host system, and presto, the site is now available on both the host and the client.

    Once again, thanks for the ideas, folks.
Sign In or Register to comment.