"Sooty" <atuczoo20@dsl.pipex.com> wrote:
>Hi
>
>this is probably off topic but don't know where else to post it...
>
>I use D-Link wireless ADSL/router/switch 604T model 54mb at home/office.
I have no familiarity with that model, so this suggestion is
purely speculation (based on having the same basic problem with
a Linksys WRT54G the first first time I fired one up).
....
>I selected LAN as connection for IExplorer and typed in the router's address
>as have done before....no connection.. "unable to display page" bring home
>the unit and try it out just in case it was DOA. Perfect connection first
>time?????
....
>the router into it and all PCs see each other no problem but cannot access
>the router's management via the http://192.168.1.1 address.
First try to ping that address. If it works, skip the rest of
this because something else is the problem!
If you can't ping the address, you've got a routing problem
caused by having your PC's IP address assigned by some means
other than DHCP from the wireless router, and it just happens to
be an address that the D-Link will *not* routed to.
So for example, the default router IP address is 192.168.1.1,
and maybe it will hand out addresses from 192.168.1.2 to
192.168.1.254 to any client (or more likely a smaller range).
It will route to that address range too. And whether you use
DHCP or not, *if and only if* your PC happens to be in that
range will you be able to ping the router or access the web
server.
If you are using static addresses or DCHP server elsewhere on
your home network and just happen to have an address in the
right range, it will work. You then take it to the customer's
more complex network and they are using address in the 10.0.0.0
subnet, or the 192.168.2.0 subnet, and it won't work!
Also, the DHCP address range and maybe the routing range may not
be the entire subnet range. A Linksys WRT54G out of the box
will not route to 192.168.1.30 for example, but will route to
192.168.1.110. The D-Link could have something very similar.
The solution is to initially access it with either a static
address in the right range, or let it provide you with an
address via DHCP. Then reconfigure it to route as needed,
and then go back to the normal IP address on the PC.
--
Floyd L. Davidson <http://www.apaflo.com/floyd_davidson>
Ukpeagvik (Barrow, Alaska)
floyd@apaflo.com