All four office PCs and the printer all depend on obtaining an IP address from the DHCP server in order to access the network. Since they are not getting a valid IP, they can't see each other, nor can they access the internet. Worse yet, users can't even get to their own files because they are stored on shared folders on the server (Paul), which they cannot see either. I don't know why the PCs can't see the router to get the IP.
So it looks to me like there is some issue with the Linksys and/or modem, but i'm not sure if it's connectivity, or something with the units themselves. Since I can't even ping them, I'm wondering if it's connectivity, but not sure why since the router shows active connections and blinks the lights like I would expect. Not a very scientific evaluation, but nothing looks obviously wrong.
The setup is an Actiontec DSL Modem (from Qwest), attached to a Linksys Cable/DSL Router. The Linksys is set up as the DCHP server, and all of the church computers (named Matthew, Mark, Luke & John) and the network printer are set up to obtain their IPs automatically. The only exception is the server in the network closet (named Paul), which is hard coded to 192.168.0.101.
The Linksys and Actiontec are both supposed to be accessible via a browser. The Linksys is at 192.168.1.1 and the Actiontec is at 192.168.0.1. I was unable to connect to either last night from any machine. If you run 'ipconfig /all' on any of the auto-IP computers, you'll see the 'default' ip address that they set when then can't find a DCHP server to get a real address, so I take that as more evidence that nothing is getting through to/from the Linksys.
Checked all the physical connections, network ids, workgroups, etc. and everything looked good. Rebooted the server, reset the router, powered everything down and then back on again... everything that normally works for me didn't.
|