Page 1 of 1

Issues when wireless is enabled

Posted: Fri Mar 11, 2016 4:58 pm
by tmm72
I am running into a weird issue with my wireless and LAN network.
What I have done is setup the LAN and have had that running for sometime now.
Recently I have setup the wireless that uses the local bridge that LAN devices are working on.
What I am having a issue with is a printer that will not respond when the wireless is enabled.
It will respond to pings etc but I can not print to it or access the web interface on the printer until the wireless is disabled.

What did I miss and what information do you need to assist me in diagnosing this issue.

Thanks in advance!

Re: Issues when wireless is enabled

Posted: Fri Mar 11, 2016 5:05 pm
by ZeroByte
Does the printer try to use wireless as well? If so, then try disabling that.

Otherwise, this seems like an IP address duplication somewhere - but I don't know why enabling wireless would lead to such a thing.

Re: Issues when wireless is enabled

Posted: Fri Mar 11, 2016 5:11 pm
by tmm72
No printer is not wireless.
The printer is getting it's IP from the DHCP pool

Re: Issues when wireless is enabled

Posted: Fri Mar 11, 2016 5:16 pm
by ZeroByte
Do you have horizon=X values applied to the ethernet ports or wlan port in your bridge > ports configuration? (doubtful, but this behavior is pretty strange) - if so, then you probably want to clear those out.

I'd say to look at the ARP table on a computer when the printer will work, (arp -a from a DOS prompt) and compare it with the MAC address you find when the printer is not working.

I'm assuming you mean "wired PC cannot talk to wired printer whenever router has wlan1 activated" - is this correct?

Re: Issues when wireless is enabled

Posted: Fri Mar 11, 2016 5:36 pm
by tmm72
Well the site is remote and they have thin clients on the network.
I can see in the torch on the bridge local network that is trying to talk to the print server but nothing.

Re: Issues when wireless is enabled

Posted: Fri Mar 11, 2016 9:00 pm
by tmm72
It seems even though DHCP was handing out addresses something on the network is trying the same ip that was setup for the printer (which is handed out by the router). So changed the DHCP pool addressing range and it seems to have fixed the issue.