Small network running Unix server - DSL install question 2

[Hueby]

Hi everyone,

We have a small network of 6-8 computers. We have a central Kingston EtherRx workgroup hub and a server used to run Unix for our old accounting program. All the computers are running Windows 2000 / XP.

We now have a DSL connection. I'm not a network expert here, but can we simply run a cable from the DSL modem into the hub and fiddle with some basic networking setting in windows to provide internet access to everyone?

I guess i'm tryin to understand that as long as we plug into the hub with the modem, then the hub can split up the bandwidth okay? Even with a Unix server there for running the Accounting program?

Thanks for any help, or guidance!

 

[bcastner]

Be wary of modems that have router capabilities. I have seen a lot of frustrated users where the default subnet for the modem/router (usually 192.168.1.x), was identical to the default subnet of the additional router.

Try:

1. Connect directly from PC to router
2. Access the web-based setup pages of the router. (Should be in the manual)
3. Change the local LAN subnet addressing of the router from 192.168.1.1, (or whatever), to:
10.0.0.1 Subnet Mask 255.255.0.0, Gateway 0.0.0.0
4. Set the router to obtain its IP address from the Modem through DHCP

My preference would be to place the Modem in pure Bridge mode, but see if this does not sort the issue.

 

[edfair]

You want to get a cable run of any type working. Once you know you have a good run then you can start swapping in stuff in segments and swap patch cables around until the entire run is working again, then go to the next segment.
Can't really give any more detailed instructions. This is elementary troubleshooting.
Might help if you had a cat5 tester set. Lights and signals on one end blinking in sequence. You plug the other end and see if the same sequence shows up.
Just because the wires are punched down doesn't mean that they are fanned correctly. My last follow behind was about 85% right.
You need at least one circuit working. Otherwise how will you know that the other circuits are not working?

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[bcastner]

My concern is that he may well be facing two DHCP servers (modem + router), all on the same subnet.
This is very common.
I wish the router people would by default use an IANA private subnet different than what the modem people choose as the default.

 

[edfair]

Agree with the long term concerns. But for now there are short term issues, pinging from one machine to one router via 2 patch cords and a cat5 drop instead of 1 long patchcord.

 

[Hueby]

Thanks guys, I'll try these suggestions and play with it some more. I greatly appreciate it!

 

[Hueby]

Well, I'm back... I tried playing around with the cables some more.

I've found that when I go through the patch panel to the router, that is when I loose any communication. Now, the old network that is going through the patch panel to the exisiting hub works fine.

But when I tried the computers going through the patch panel to the router, I couldn't ping - but it did show a "activity" light on the router. I started switching cables around, etc. with no luck.

So, I guess I'm wondering why it isnt working when I go from the patch panel over to the router, but going to the hub it works...??

..and, what do you even really need the patch panel for? Is it really needed, or can I just run straight cat5 from the computer to the hub.........??? Thanks!

 

[edfair]

Sounds like you need to get some info about your router. It has the capability to block stuff.

You can string cable directly. Just makes a mess sometimes. And if you are using solid wire they tend to break when flexed in movement. If using stranded it cuts down on the distance.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[Hueby]

Well, the router is just a cheap D-Link 603 model or something. ???

I have tried several different cables, including new cat5.

Thanks...

 

[edfair]

And a setup program for it?
Can you ping it and get a response? Got to be able to talk to it before you can talk through it.
Use a tracert to try to get to another box.
And if using router supplied IP addresses, are you getting them on all boxes?

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[Hueby]

I can get through the setup program when directly connected to it. It is setup with PPPoE for the SBC DSL. I can get online, etc. fine. I changed the router lan subnet to 10.0.0.1 as suggested.

That's all I've really played with a lot for the router setup.

IP addys are dynamic.. I'll have to check if they are getting out okay then.

I can ping it just fine UNLESS i go through the patch panel.

Thanks Ed!

 

[edfair]

Then it looks like the part of the cabling is bad or you have a crossover for one of the patch cables.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[Hueby]

Well, rather then screwing with this darn hub or patch panel, there wouldn't be any problem with just removing the patch panel and diching the hub as well. Then buying a 12+ port router and running cat5 directly from the computers to the router?

 

[edfair]

No







Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[Hueby]

While I'm here... would there even be any advantage to using a switch instead of a router when dealing with 8-10 ports?

 

[franklin97355]

Routers and switches are two different devices. Some equipment combine them in one box though.

 

[Hueby]

Thanks, the situation is, I need 9 ports open.. and most routers are 8 port. And it seems after 8 ports they are really expensive! I guess a cheap hub for 2 of the computers to share one of the ports on the router would work huh.

 

[franklin97355]

Small switches are not much more than hubs these days. (If you can still find hubs in the consumer market)

 

[Hueby]

Thanks Franklin,

Let me throw out one more question/concern. I get all the computers, including the Unix server, hooked into one Router (with the DSL modem providing internet)... do I need to set all the PC's IP address manually in the router setup?

I need to keep the IP's set manual on all the PCs so the Unix Server accouting software will work. When they are set dynamic they can't find the Unix Server.

So, unless I can setup that up differently... I will keep the PC's manually set on IPs, and setup the router for manual IPs correct? Thanks

 

[edfair]

You don't set it up in the router, you set them individually on the PCs.
But there is the question of why the PCs can't see the Unix. What software are you using as the terminal? Whatever you are using should be configurable to reach. And the router should be able to define the limits of IP addresses that it will parcel out.

Ed Fair
Give the wrong symptoms, get the wrong solutions.

 

[Judbud]

I'm having same problem!
I need to keep the IP's set to static ip's on all the PCs so they can access the Unix Server software. When they are set dynamic they don't see the Unix Server. If router is set to dhcp I can access the internet from all machines but they have to be set to obtain ip automaticly to work on the net, but then theres no access to the unix software??

With dhcp disabled on the router. I think i'm putting in the wrong static information into the router?? There are 2 switches and 1 router both the switch#1Unix and router#1Netgear are plugged into switch#2(16portnetgear)
having to keep my users ip's to static in the range of 192.168.1.161-192.168.1.164 to keep access to the co. software, I'm not sure what static information i need to put into the router?? to see the internet. Any help Welcome