• We’re currently investigating an issue related to the forum theme and styling that is impacting page layout and visual formatting. The problem has been identified, and we are actively working on a resolution. There is no impact to user data or functionality, this is strictly a front-end display issue. We’ll post an update once the fix has been deployed. Thanks for your patience while we get this sorted.

Router/Hub and Static Routing Question

P

Padriac

Golden Member
1) I have a umax ugate 3000 4 port 10/100 router. I currently have 3 machines in my house that I am trying to share the internet with.
2) My main box is upstairs. It has both the cable modem and router side by side and the cable modem out is going into the first port on my router. Its internet is working.
3) They I have about 100ft of cable going to my downstairs from the second jack of my router and into that machine. Its interenet is working.
4) However, I also would like to have access to the internet from my other downstairs machine but would prefer not to re-run another long length of cable.
5) So I pulled out a hub I had and unplugged the cable in the second port of my router and moved it over to the uplink part and plugged it into the router downstairs.
6) I then proceeded to run cable to both my downstairs machines from the hub.
7) I then set the static routing table in my routers menu to the following

Destination LAN IP ----- 192.168.0.0
Network Mask ----------- 255.255.255.0
Gateway IP -------------- 192.168.0.1

8) One of my downstairs machines... the one that originally worked is up and running no problem. Here is the information gathered from my ipconfig of that machine. WIN2000

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 192.168.0.3
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1

9) However this is the same info from the other machine plugged into the hub. WINDOWS 98

Ethernet adapter Local Area Connection:

Connection-specific DNS Suffix . :
IP Address. . . . . . . . . . . . : 169.254.241.218
Subnet Mask . . . . . . . . . . . : 255.255.0.0
Default Gateway . . . . . . . . . :

10) Where are these numbers coming from??? They don't seem to correspond to anything I have done.

WHAT I HAVE TRIED
---------------------------------

I have tried different cables, nics, and plugging the working cable into the other machine. So basically I THINK I have eliminated any problem with regards to hardware.

Please feel free to let me know what I am doing wrong and provide me with some solutions I can try. Perhaps I need another entry in my routing table... anyone???

PLEASE I NEED MY NET





 
Well, the 169 address is because the machine is set up to get it's address via DHCP, and it can't see or get information from the DHCP server. That means it's gotta be a cable or bad connector...it's a straight run to the hub/switch, right? no intermediate machines? If you're going hub to hub, then you need a crossover cable......are you getting link lights at both ends (NIC and hub/switch)?

IF you're getting link, but still not talking, try manually setting the speed at the NIC to 10 MEG half duplex (the cable may be good enough for a link, but crappy enough where it won't get high-speed data through.

AND BTW: get rid of the static route. You have a static route that points to itself....if you're going to do one like that, try address "0.0.0.0" with a mask of 0.0.0.0 ....that would send all non-local traffic to the default gateway/next hop. Connecting hub-to-hub means you still have one broadcast domain (and if they're really hubs, one collision domain).....it's still one big network. Lose the static route.


Let us know.....


Scott
 
Thank you very much for responding.

Will try what you said when I get home from work.

Another thing is when you answer could you please be VERY VERY specific because I'm new to all of this crazy networking stuff.

What you're saying I should try is:

Destination LAN IP ----- 0.0.0.0
Network Mask ----------- 0.0.0.0
Gateway IP -------------- 192.168.0.1

If not let me know what you meant?
 
You shouldn't need any static route on your router. All of the outbound traffic is going to one spot (your ISP), all of your inbound traffic is going to one LAN...that being the case, you shouldn't need ANY static routes.

IF ANYTHING, you'd want to point to a "Default Gateway," which is usually represented as address "0.0.0.0" with a mask of "0.0.0.0" then the next hop (the next address in the chain that the traffic should be routed to).

When your LAN PC is getting ready to send traffic somehere, the first thing it decides is whether the packet is going to somewhere on the same LAN, or off-LAN. If it's going off-LAN, then the PC puts the Default Gateway MAC address in the destination field of the packet, the packet gets to the router, the router decides where it's gotta go next. If the router doesn't know specifically where the destination address (the IP address) is, but it DOES have a "Default Gateway" address, then the router will put the MAC of the (next) default gateway in the packet and send it on to the ISP's router. The process is repeated until the packet gets to where you sent it, or it "times out" one way or another.....in which case your system repeats the process after its timer expires.

So, the LAN PCs need a default gateway setting for the router (the "Next Hop"), and the router needs a default gateway setting to the ISP (the "next hop" from the router to the ISP). Since your LAN is directly attached to the router, when traffic arrives with a destination on your LAN, the router will know where to send it. NO STATIC ROUTE IS NECESSARY FOR THE INBOUND TRAFFIC. If you have a Default Gateway set in the router, no static route is needed for the outbound traffic.

If you were set up to send some traffic to a specific address block (like your company via VPN) and the rest of the traffic was going somewhere else (like the Internet), then a static route would be a good thing. With one destination on either side of your home router, no static routes are required...and are likely to screw things up.

There is also a process I didn't mention (not really relevant) called ARP - Address Resolution Protocol, that finds out what hardware address is associated with which IP address. It's automatic and there is no configuration necessary on your part....but if I didn't mention it, someone else would...it's irrelevant to this discussion.

SO...bottom line, remove your static route, verify that the PCs are aimed at the router, and the router is aimed at your ISPs router (both will be default gateways PC-->Router-->ISP).

Good Luck

Scott
 
You must log in or register to reply here.

TRENDING THREADS

Back
Top