I have 2 systel systems that are networked through an Ethernet Switch. The systems have IP addresses that are set. I want to add a wireless router that will be on a desk, rather than in the Rack where the switch is at. That will give users at the desk who do not have wireless access a place to plug in to the router. However, I'm obviously not configuring the router correctly because it's not seeing the other 2 systems. I'm not sure if it's seeing the switch or not. I don't know much about switches because this is the first time I've had to deal with a switch. What are some things that I have to keep in mind to work the router into the network that is currently using the switch?

You have a wireless router for those who can't use wireless but can hook up with a lan cable? Doesn't sound like you need the router at all. Why haven't you just cabled then to the internet router you are presently using???

Some people have wireless systems. That's why I have the wireless router. However, some don't have wireless systems, instead of running a separate cable from the switch to the work area for each system, I'm only running one cable to the router, then they can plug into the router. This system isn't connected to the internet on a regular basis, because it's mounted in a mobile unit. I currently don't care if they can access the internet as long as all the systems can communicate with each other. I've never used an ethernet switch before, so I'm trying to find out how I have to configure my router to work with the switch.

A switch just connects things with LAN cards (might be built in): computers, wired routers; LAN printers; print servers; etc. There is nothing to configure on the current generation of switches other than the very high end layer 3 ones. If you have a router with enough ports then you don't need the switch. A switch is just an intelligent hub, if that helps at all. I suspect you have a problem with your subnets. All the hosts and the router have to be on the same subnet/mask in order to see each other. Peter

Thanks for the info. I guess I just need to get the settings on my router correct. Can I have a fixed IP for my router, and have my router assign IP addresses for all systems that I hook up to it? Also, should I hook up the cable from the switch to the internet port on my router or to one of the other ports? Here's the scenario: I have a server and a work station in a van. They're rack mounted. I have a MAU for the token ring, and a 16 port ethernet switch for the lan. The 16 Port Ethernet switch is actually overkill, since there are only 2 systems, but that's what my company sent me. The reason I want the router is to give an access point away from the rack and only have to run one cable from the rack to the work area. At the work area there will probably be at least 2 systems hooking up to the network, and possibly a third or fourth hooking up wireless. I'm pretty sure now that the problem does lie in the router settings, because last night I hooked my system up directly to the Switch and after giving my laptop an alternate IP configuaration, I was able to access the server. So I just need to get the router to access the server and I'll be in business.

I think we should define our terms. "Router" has changed meaning over the last year or two to include ADSL/CABLE modem integrated with a 4 port switch as well as an actual router all in the same physical case, with its primary purpose to connect 1-4 computers to the internet. Plain old routers simply connect subnets. Now your term 'system' means exactly what? Do you mean a computer system or do you mean a subnet (different from another subnet on same LAN)? *If* it is the first, and all the hosts are on the same subnet and all you want to do is have one instead many UTP cables going to some distant computers, then you plug in one cable from the 16 port switch to a local switch, and the local computers into that local switch. No router need be involved. If it runs outdoor then there are some hardware issues. If you simply want to give wireless computers access to a wired LAN, then all you need is a wireless bridge and of course the wireless client hardware on the computers. Again, there is no router. If the subnets are different then you need a router (not a modem/router combo) to deal with that, which is a bit of a PITA. "Can I have a fixed IP for my router, and have my router assign IP addresses for all systems that I hook up to it?" This indicates to me that everything is on the same subnet, and the answer is 'yes'. If they all need to have internet connection then the logical way to connect them is ADSL ->router ->16_port_mobile_switch ->local_switch and you should be sure the router also assigns gateway and DNS servers. Are we closing in on a solution yet? :-) Peter

Yes, thanks again for all the information. Turns out that the problem with the router is that I wasn't using the correct IP for it. My Default gateway on all the computers was 192.168.0.254. Well, I finally realized that the router is the gateway..........lol. So it's all running now. And yes, all the computers are on the same subnet. They've had problems with connecting to the internet at another location, and I was kind of wondering about that, but they are only using the switch and don't have a router in thier network at all. I'm not too worried about the internet connection right now because it doesn't really affect how the system performs it's job in the field, but I'm sure it will work fine on the internet through the router. Thanks again for all the information.