On Mon, 2009-11-09 at 14:17 -0500, Dennis Mattingly wrote: > >> So I finally think it's a hardware issue. > >> > >> Thanks for all the input. > >Routers normally have their own static addresses (different for > >different router companies) which allows you access their > configuration > >interface. > > Some network-admins at my job examined the router and it looks like a > hardware issue. > Not only did they confirm the LED lights are very dim, but they > couldn't detect the router using any hardware / OS / computer / > network cable. > > So thanks again all for your help. > I'll go to Microcenter soon and purchase a nice new LinkSys router. > > I heard someone mention NFS and static-IP addresses. > So I'll start playing in that ballpark and see how far I can go. > -- Cool. In most routers you can set where the DHCP scope starts so when you create a server (for NFS or whatever else you want) just give it a static IP outside of the DHCP scope. For example, a router has an IP of 192.168.1.1 gives a scope of 192.168.1.100 to 192.168.1.200. You can use any IP from 192.168.1.2 through 192.168.1.99 and 192.168.1.201 through 192.168.1.254. The gateway would be 192.168.1.1 for this router setup (coincidentally the same as most Linksys routers). The documentation that comes with the router will tell you what to do, don't bother using the CD but power it up, plug in your modem and connect a PC to it and set the PC to use DHCP. You will then be able to access the router and set it up that way. After which you can google for "linksys DHCP scope" and should get lots of info that way. Good luck! PS. I have had a lot of Linksys equipment die on me, for a pretty solid router I would go for the Dlink DIR-655 extreme, 4 x gigabit switch is integrated and it is around $120 CAD.
Attachment:
signature.asc
Description: This is a digitally signed message part
-- fedora-list mailing list fedora-list@xxxxxxxxxx To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list Guidelines: http://fedoraproject.org/wiki/Communicate/MailingListGuidelines