Java Jive!

Collapse
X
 
  • Time
  • Show
Clear All
new posts
  • cphilip
    Former Moderator

    • Jun 2026
    • 16216

    #31
    Nope it is a simple hub. However like I said it used to work with all the clients and the Gateway set to 192.168.0.1. The first time I ever set up this home network it did. It then did this "scrambling" one time before and I could only get it back up running by assigning sequential IPs to it. It would not let me assign them all the same that time. And by trial and error I stumbled across that fact that it did work with sequential IP's For some strange reason it worked. So I was happy enough to leave it alone then and not question it. But this time it will only bring in Internet copnnection. Why I do not know. Why it worked with sequentials last time I do not know. I do not know. However because it was trouble free at the time I was not going to question it! This time it appears I will have too.


    AGD, where we are so good we can do it with only ONE tube!

    cphilip.com

    Comment

    • cphilip
      Former Moderator

      • Jun 2026
      • 16216

      #32
      Ok I did find this and it may be applicable I do not know...I do no think so as this has been up for a few months and mine was working and the client machine is still working but see if you see anything in here that may be related if you would. I do not fully understand the language here. This tcp2http stuff? it does state the work around only will work on the modem conected gateway and unless I can get my others to accept the same IP then It may be they are not routing through for this reason. SO the problem may be narrowed down to why is my gateway not allowing me to assign the same IP's to the clients. That may be the root of all my problems.

      This applies to the 360 Network only:
      Starband has blocked tcp2http from routing data through their HTTP Proxy servers. Actually something to understand here is that not only does this affect tcp2http, but any program that tries to route non-cern based http commands through the router, these programs include Socks2http and any program that has the option to connect through an HTTP server such as ICQ.

      The work around for this in tcp2http is to go into the config screen and place a checkmark in the "Bypass proxy server" option. This will only work if the tcp2http copy you are using is located on the 360 connected computer.

      Starband is stating that the HPA servers were not meant to handle anything other than HTTP traffic, thus the additional load that tcp2http is putting on these servers is having a negative impact on those who are merely trying to browse the Internet. Most of this additional load appears to be from those who are downloading large binaries from the newsgroups.

      Starband has already implemented these changes, so this is a done deal. Remember you will still be able to use tcp2http by checking the "Bypass Proxy" in the config screen.


      AGD, where we are so good we can do it with only ONE tube!

      cphilip.com

      Comment

      • Shirow
        www.digitalgunfire.com
        • Aug 2002
        • 2023

        #33
        Nope it is a simple hub. However like I said it used to work with all the clients and the Gateway set to 192.168.0.1. The first time I ever set up this home network it did. It then did this "scrambling" one time before and I could only get it back up running by assigning sequential IPs to it. It would not let me assign them all the same that time. And by trial and error I stumbled across that fact that it did work with sequential IP's For some strange reason it worked. So I was happy enough to leave it alone then and not question it. But this time it will only bring in Internet copnnection. Why I do not know. Why it worked with sequentials last time I do not know. I do not know. However because it was trouble free at the time I was not going to question it! This time it appears I will have too.
        Well, you must be doing something to share the Internet connection then - a plain hub with no proxy server or ICS software wouldn't let you get online with a 192.168.x.x address, as they are private network addresses and are not Internet routable. You'd have to have a proxy or something doing NAT for that to work.

        If all the clients were set to the same IP address, it makes even less sense - how would any of them be able to talk to each other?

        If you have a router doing NAT and you assign each client a different 192.168.x.x IP address, the outside world still sees them all from the same public IP address. The public IP address (let's call it 1.2.3.4 for the sake of argument) would be assigned to the router. The router would then either assign 192.168.x.x to the clients via DHCP or you would assign them statically. Then, when a client with 192.168.1.5 for example wanted to get online, any contact that client made with the Internet would come from 1.2.3.4, the IP of the router. The router would also have an internal IP of 192.168.1.1 though.

        Whatever you are using as your gateway is doing the NAT for you. A hub cannot have an IP address, and cannot be a gateway - it's just a piece of hardware used to connect multiple computers together.
        Last edited by Shirow; 10-01-2002, 08:33 AM.
        Superbolt

        Comment

        • cphilip
          Former Moderator

          • Jun 2026
          • 16216

          #34
          True the gateway is acting as the router...And is sharing but in this case stingie with that!


          AGD, where we are so good we can do it with only ONE tube!

          cphilip.com

          Comment

          • Shirow
            www.digitalgunfire.com
            • Aug 2002
            • 2023

            #35
            So what I would do would be to go into your gateway, set the DNS server information to be obtained automatically, set the WAN IP address to be obtained automatically and set the router to assign private ips to your network via DHCP. Then set each client to automatically obtain a private IP and DNS server information. This should ensure you have the most up to date information.

            If this still doesn't work.. try the nslookup thing I posted earlier.
            Superbolt

            Comment

            • cphilip
              Former Moderator

              • Jun 2026
              • 16216

              #36
              Ok will try that...in that order. Not sure I have not already as I am starting to forget all the things I tried.

              The Starband guru's are telling me I must point them all to the same IP again but I am waiting for them to figure out why they will not take it and they recognize that its already assigned and will not allow it to be used. It may be a sequence out of order I am doing it in. But they agree that its ICS on the gateway and all the clients do need to be pointing to 192.168.0.1 and at this point they are not and will not.


              AGD, where we are so good we can do it with only ONE tube!

              cphilip.com

              Comment

              • Shirow
                www.digitalgunfire.com
                • Aug 2002
                • 2023

                #37
                All the clients need to point to 192.168.0.1 as the gateway.. I have absolutely no idea why they would tell you to give them all the same IP address though, unless they are using some really, really bizarre proprietary piece of equipment. All clients have to have different IP addresses.. it's like a telephone number. If 10 people have the same phone number, who would you get when you called that number?

                Let me know what happens, my interest is piqued
                Superbolt

                Comment

                Working...