I have a DLink router/firewall (LinkSYS makes similar devices) connected to my DSL, then 4 computer plugged into it. for the most part, everything works fine. I have the DLink set up on the LAN as 192.168.0.100. I can ping it from all 4 boxes, all 4 boxes can surf, telnet, etc...

if I go to http://192.168.0.100 I'm supposed to be able to bring up a administrative configuration page. i can bring up that page from 3 of the 4 boxes. from this box (roadking) I cannot see that page. i get a connection refused message. a tail -f of /var/log/messages during an attempted connection shows:

Dec 2 14:33:13 roadking kernel: fw-L-o Generic Drop for Outg IN= OUT=eth0 SRC=192.168.0.1 DST=192.168.0.100 LEN=60 TOS=0x00 PREC=0x00 TTL=64 ID=0 PROTO=TCP SPT=43417 DPT=80 WINDOW=5840 RES=0x00 CWR ECE SYN URGP=0

any ideas?

try 192.168.0.100/001

My cable router/firewall will not show unless I do this. Works fine from a windows machine when I was dual booting. Now I have to do that up to 010 to view all the pages.

I immediately get a "The connection was refused when attempting to connect to 192.168.0.100" dialog. the connection is being refused by the server??? I can ping it, go through it to use the net, but can't configure it from 1 out of 4 boxes. odd.

Did you ever set it up or did u just start using right out of the box? If you configured it prior to using it you may have set it up to do that. If so try using the reset switch/button to reset and then reconfigure it. If all else fails they have a number toll free that u can call for help
1-877-453-5465

The process for resetting the DI-713P router ( I imagine this procedure is pretty common across D-Link routers) is to:

- insert a paperclip or other thin straight object into the
reset hole and push in - hold that while you

- unplug the ac power cord

- go get a cup of your favorite liquid ( yes, you can put the
paperclip down )

- return and plug the power cord back in

- reconfigure the router ( password, access control, etc. )
.
It's relatively painless and you can't seriously screw anything up

a reset solved this issue, thx.