Our fire station has a cat5e cable supplying internet access to our internal network from a switch in city hall. It connects a baystack 350 to their switch. If this cable is left plugged in during the...
Very likely an IP problem. The server in City Hall is most likely doing the DHCP assignments for all connected machines, and if there is a LAN server running DHCP also in the firehall, there will be a conflict, which may not manifest itself until the assigned IP leases expire and renew. If this is the case, try a router WITH DHCP DISABLED between the two systems, WAN side toward City Hall. As a quick test, disconnect the cable and run IPCONFIG on a firehouse machine. Note the IP, it should begin with 10, 172 or 192. Reboot the machine, run IPCONFIG again. If the IP comes back, you have DHCP running on something. If you see something like 169.254.???.??? you do not, in that case try hooking up a router configured just as it comes from the box. If anything in the firehouse is wireless, making connection thru a wireless router, the problem may be a simple miswire. WAN side toward City Hall and one of the ports toward your switch, don't use the other three. May need to use the uplink port or a crossover cable between router and switch. (Network admin by day, DJ by night)
Sep 11, 2008 |
Computers & Internet