if your peripherals aint talking to a particular connection
walk it back. Start at the peripherals and go through each gateway and see if the message is getting through at each step. That will identify at which point the failure is occurring. then check the logs of the failing device and if that doesn't show anything add more logging.

/generic computer advice
( The Light in Chains don't touch the Pope's boner, Fri 21 Mar 2014, 23:40, 2 replies, latest was 10 years ago)

Lighty *nods*

( hartley hare Just some prick who thinks it doesn't apply to him, Fri 21 Mar 2014, 23:45, Reply)

hh
*finger points*
( The Light in Chains don't touch the Pope's boner, Fri 21 Mar 2014, 23:53, Reply)

You off to Jeffstock
Is Monty and Stunned going?

Is Stunned the DD?
( hartley hare Just some prick who thinks it doesn't apply to him, Fri 21 Mar 2014, 23:56, Reply)

monty can't, Stunned is
www.nndb.com/people/877/000022811/rodney.jpg
( The Light in Chains don't touch the Pope's boner, Sat 22 Mar 2014, 0:02, Reply)

Yeah well give Jeffers a big wet sloppy kiss from me yeah
and if B3th turns up tell her I said she is a shit mod
( hartley hare Just some prick who thinks it doesn't apply to him, Sat 22 Mar 2014, 0:09, Reply)

*nods*
start with the physical (wires etc),then basic network (ping test etc), then work up to the more complex stuff like DHCP, NAT, etc.
Anything static addressed?
(localboy purveyor of pisspoor puns, Fri 21 Mar 2014, 23:53, Reply)