Cannot acess web interface on any of my routers on network??

[steve]

I have several wirerless/wan/lan routers in a couple of buildings.
They are differnt manufacturers routers. People have varying degrees
of dificulty connecting to the routers througth wifi. There is one
windows 2003 server on the network that does wins and a router in the
phone room that brings the net in and does DHCP.

Here is the problem. If connect a cable directly up to the individual
routers I can connect to the web interface of the router. But If I go
to any one of the computers in the office (accept those conected
directly to the router), I cant really connect. The best I can do is
get the password prompt where I put in admin and password but then it
trys to connect and either gives up or just sits there slowly grinding
away but never connects. I might get the title of the page on the top
of the browser like "default setup" but thats it.

Its like something on the net work is stopping or slowing the
connection down so much that it just cant connect. Of course I have
the network connection connected in to the lan ports and have actually
put tape over the wan port so no one will by mistake plug anything
into it. There are a few swtiches here and there that help to divide
up the network but thats about it.

One final this to say is that we have several copiers that have web
pages build into them and a copier, and I can access those web pages
no problem. I just dont get it.

Anyone have any ideas?

Thanks

[terryc]

On Thu, 19 Feb 2009 18:20:52 -0800, steve wrote:


> Here is the problem. If connect a cable directly up to the individual
> routers I can connect to the web interface of the router. But If I go
> to any one of the computers in the office (accept those conected
> directly to the router), I cant really connect. The best I can do is
> get the password prompt where I put in admin and password but then it
> trys to connect and either gives up or just sits there slowly grinding
> away but never connects. I might get the title of the page on the top
> of the browser like "default setup" but thats it.

sounds like default setup to me, inside net connection is allowed for
configuration, but outside wireless connection isn't.

Personally, as an admin, I can not see the problem as it gives you another
l

[steve]

Thanks for your comments.

Unfortunetely the inside allow web admin is set to allow. And the fact
that it allows me to put in the username and password and then seems
to try to connect seems to indicate that it is set up right.

Im wondering about colisions perhaps but I really dont know how to
test for this ?

Regards

[Iced Tea]

I have a Linksys router and you can only change the router settings when
directly connected (hard wired) to the router. As far as trying to change
them from a wireless connection isn't allowed.

Hope this helps,
Carl

"steve" <stevesemple@lycos.com> wrote in message
news:ee4c442e-ad00-4d24-a495-715a3cdb5247@w1g2000prk.googlegroups.com...
>I have several wirerless/wan/lan routers in a couple of buildings.
> They are differnt manufacturers routers. People have varying degrees
> of dificulty connecting to the routers througth wifi. There is one
> windows 2003 server on the network that does wins and a router in the
> phone room that brings the net in and does DHCP.
>
> Here is the problem. If connect a cable directly up to the individual
> routers I can connect to the web interface of the router. But If I go
> to any one of the computers in the office (accept those conected
> directly to the router), I cant really connect. The best I can do is
> get the password prompt where I put in admin and password but then it
> trys to connect and either gives up or just sits there slowly grinding
> away but never connects. I might get the title of the page on the top
> of the browser like "default setup" but thats it.
>
> Its like something on the net work is stopping or slowing the
> connection down so much that it just cant connect. Of course I have
> the network connection connected in to the lan ports and have actually
> put tape over the wan port so no one will by mistake plug anything
> into it. There are a few swtiches here and there that help to divide
> up the network but thats about it.
>
> One final this to say is that we have several copiers that have web
> pages build into them and a copier, and I can access those web pages
> no problem. I just dont get it.
>
> Anyone have any ideas?
>
> Thanks

[terryc]

On Mon, 23 Feb 2009 08:05:05 -0800, steve wrote:

> Thanks for your comments.
>
> Unfortunetely the inside allow web admin is set to allow.

And the outside?

Inside on my WAP means the ethernet and outside the wireless part.


The other problem could simply be your browser. I have met some of thes
boxen that only work with IE, etc.


> Im wondering about colisions perhaps but I really dont know how to test
> for this ?

This would only be a problem if you have a busy wap and it would show with
other clients.

[steve]

On Feb 23, 8:06*pm, terryc <newssevenspam-s...@woa.com.au> wrote:
> On Mon, 23 Feb 2009 08:05:05 -0800, steve wrote:
> > Thanks for your comments.
>
> > Unfortunetely the inside allow web admin is set to allow.
>
> And the outside?
>
> Inside on my WAP means the ethernet and outside the wireless part.
>
> The other problem could simply be your browser. I have met some of thes
> boxen that only work with IE, etc.
>
> > Im wondering about colisions perhaps but I really dont know how to test
> > for this ?
>
> This would only be a problem if you have a busy wap and it would show with
> other clients.

Thanks for your thoughts.
I understand what your saying about inside and outside and wifi, in
either case Ive allowed everything to try to resolve it at lease till
i get it working right. Still no luck.

I have tried other browsers but no luck same for firefox and IE

I think what your saying is that if there were colisions there would
be problems elseware. There are some problems but when I connect via
wire there are no problems. Wifi there are variing issues.

I took one of these routers and put it on my home system and it works
fine. Its something about the network its on. I done really know how
to debug it. I may try some software but I really dont know what I
would be looking for.
Regards

[GlowingBlueMist]

"steve" <stevesemple@lycos.com> wrote in message
news:97c47ed6-1485-4761-ac75-fd3f84c9376d@m22g2000vbl.googlegroups.com...
On Feb 23, 8:06 pm, terryc <newssevenspam-s...@woa.com.au> wrote:
> On Mon, 23 Feb 2009 08:05:05 -0800, steve wrote:
> > Thanks for your comments.
>
> > Unfortunetely the inside allow web admin is set to allow.
>
> And the outside?
>
> Inside on my WAP means the ethernet and outside the wireless part.
>
> The other problem could simply be your browser. I have met some of thes
> boxen that only work with IE, etc.
>
> > Im wondering about colisions perhaps but I really dont know how to test
> > for this ?
>
> This would only be a problem if you have a busy wap and it would show with
> other clients.

Thanks for your thoughts.
I understand what your saying about inside and outside and wifi, in
either case Ive allowed everything to try to resolve it at lease till
i get it working right. Still no luck.

I have tried other browsers but no luck same for firefox and IE

I think what your saying is that if there were colisions there would
be problems elseware. There are some problems but when I connect via
wire there are no problems. Wifi there are variing issues.

I took one of these routers and put it on my home system and it works
fine. Its something about the network its on. I done really know how
to debug it. I may try some software but I really dont know what I
would be looking for.
Regards

I have seen similar problems when multiple routers were set for the same
address. If say the more than one router is using the IP address of
192.168.1.1 then more than one might be trying to respond to your LAN
connection request causing what appears to be colisions.

Verify each wireless router is set for different subnets like 192.168.1.xxx,
192.168.2.xxx, etc.

[GlowingBlueMist]

"GlowingBlueMist" <nobody@nowhere.com> wrote in message
news:49a48c6a$0$90266$14726298@news.sunsite.dk...

> I have seen similar problems when multiple routers were set for the same
> address. If say the more than one router is using the IP address of
> 192.168.1.1 then more than one might be trying to respond to your LAN
> connection request causing what appears to be colisions.
>
> Verify each wireless router is set for different subnets like
> 192.168.1.xxx, 192.168.2.xxx, etc.
>
Darn, forgot to edit the source to make it easier to read... Sorry.

[steve]

> > I have seen similar problems when multiple routers were set for the same
> > address. *If say the more than one router is using the IP address of
> > 192.168.1.1 then more than one might be trying to respond to your LAN
> > connection request causing what appears to be colisions.
>
> > Verify each wireless router is set for different subnets like
> > 192.168.1.xxx, 192.168.2.xxx, etc.

Well they are all different IP's eg different host numbers, but not
subnets.
1.200 , 1.201 , 1.203

While it would be an intersting test to change the subnet, It should
work with the same subnet. I also am not sure if I change the subnet
Im not sure I will be able to connect to the router web page from say
192.168.1.10 to 192.168.0.200.

regards

[terryc]

On Tue, 24 Feb 2009 11:26:07 -0800, steve wrote:

> I think what your saying is that if there were colisions there would be
> problems elseware. There are some problems but when I connect via wire
> there are no problems. Wifi there are variing issues.

What I am saying is that if there are wifi only problems, then all other
boxen using the wifi link should have that problem.

Welcome to the world of trouble shooting in wifi where reo in a concrete
beam can affect stuff.

Tried moving the wap up higher?


can you run a tcpdump and workout what the packets are doing
>
> I took one of these routers and put it on my home system and it works
> fine. Its something about the network its on.

Naah, more like the location, unless you are still chasing up a
configuration problem.

[GlowingBlueMist]

"steve" <stevesemple@lycos.com> wrote in message
news:ba270b75-9f83-4a14-a0be-c00d354e9454@v15g2000yqn.googlegroups.com...
>>> I have seen similar problems when multiple routers were set for the same
>>> address. If say the more than one router is using the IP address of
>>> 192.168.1.1 then more than one might be trying to respond to your LAN
>>> connection request causing what appears to be colisions.

>>> Verify each wireless router is set for different subnets like
>>> 192.168.1.xxx, 192.168.2.xxx, etc.

>>>Well they are all different IP's eg different host numbers, but not
>>>subnets. 1.200 , 1.201 , 1.203

>While it would be an intersting test to change the subnet, It should
>work with the same subnet. I also am not sure if I change the subnet
>Im not sure I will be able to connect to the router web page from say
>192.168.1.10 to 192.168.0.200.

I agree that being all on the same subnet should not cause a problem as long
as the only one router is supplying ALL DHCP IP's.

You have most likely already done this, if not then verify the DHCP IP
address of the wireless PC you are testing from. First verify that the
reported problem is occurring from the PC under test. Then change the IP
address of that PC (temporarily) from DHCP to a fixed IP in the range
assigned to but not being used by your routers (having first pinged the
fixed IP you want to use to verify nothing responds. True not all devices
will or can respond to a ping but it's a start). Then from that PC try
pinging it's old DHCP address and see if something responds, provided your
PC's and any firewalls are not set to block pings. If you did get a ping
response then more than one router is assigning DHCP values or you have a
mixture of fixed IP and DHCP devices trying to use the same IP range. We
had one lab that would constantly program their stuff using the "ping test
for an unused IP value", then assign a fixed address to the device being
tested. We finally had to stick that lab on it's own subnet. One hopes for
no response to the old address but verify by trying to ping one of the other
wireless PC's elsewhere at the plant to verify the firewalls are not just
blocking pings. It might also help if you do your testing when the most
PC's are using the network. More PC powered on would mean more DHCH values
in play.

Some routers are factory set to issue DHCP values on the wireless side even
if the wired side has it disabled. If more than one PC connected wireless
using the same IP address on a different wireless router you might see what
you are describing. The better routers let you assign a range if DHCP
values on the wireless side from a common pool. Like router 1 can use
xx.xx.xx.1-25, router 2 is set for xx.xx.xx.26-51, etc until you run out of
values or routers.

As for the connecting from various subnet'd routers, you would most likely
need to load a few static route entries in the main router allowing traffic
to go from one subnet to another. If the slave routers are daisy chained to
each other then individual routers would also need a few static routes added
to them so they would know where it's possible to send data to.

One last thought, are all of the wireless routers are set to use the same
channel number? Depending on how close the wireless routers are to each
other they need to be set to individual channel numbers so as to not cause
interference.

[steve]

Thanks for your tips.
Terryc
Really is a problem in one building. I have not tested everywhere but
in a couple of places where ever I put the router people have trouble
connecting and I cant connect via web to administration. if Im not
directly connect to the routers.
odd.

GlowingBlueMist (interesting name) The ip thing is intersting and I
will have to check that if the wifi is giving dhcp despite telling it
not to. The the fact that it happens on two routers different makes
etc. seems doubfull, but I shall try to leave no stone or router un
turned.

Yes I have set them to different chanells to stop any conflict.

thanks all.