VLAN1 (Default) pings VLAN101 and a device's IP address, but it won't print to it.
Dear all,
I'm experiencing an unusual situation that suddenly started occurring on my network.
I have the OC200 V1, ER605 V2, SG2008 V4.20, and the EAP670 V1.
I work with my VLANs as an interface.
My PC is on the Default VLAN.
I was printing normally to my printer on VLAN101. My WLAN is configured on VLAN101. At least I realized something after formatting my computer and installing a new Windows image: now, to print to the printer, I need to connect to the same network as VLAN101. This wasn't necessary.
I'd like to understand this better. My Default VLAN pings all the others, including the printer. Therefore, I should have permission to access the network on VLAN 101 and consequently print.
Note: In the previous Windows format, I used the Omada software controller. I migrated from it to the OC200 for several reasons.
My dear friend.
Thank you very much.
You were absolutely right.
And that was without doing any further research.
I didn't even go to the forum.
I was very upset that accessing the printer's web address would turn it on. However, it wouldn't print.
I reset the networks and nothing.
So I decided to redo the printer driver installation process, removing and reinstalling from scratch.
And then I noticed there was an option in the drivers for connecting to the printer that gave me two options. We always want to follow the recommendation, but it's not always the answer. That's why I like to go against the rules sometimes, and it takes me a long way.
There were options for connecting to the printer through the router and connecting directly to the printer. I was going with the first option, which was the driver's recommendation. I went with the second option this time, and everything worked.
It was my own ignorance. Omada is unbeatable, as always.
My friend. Off-topic. When will we have:
1- The new, better-tuned versions of the OC200 and ER605 firmware?
2- I'm quite disappointed with the Omada market in Brazil. I see more affordable and better equipment than the ones I own outside of Brazil, but it's not available here. I'd like to have more features like IDS/IPS on my network with the product itself;
3- I don't know if I'm talking nonsense, but I find Omada's logs a bit simple. I'd like to analyze the logs in a more complete format for manual inspection. Is it possible to enable a more complete logging mode?
You can use this label to find out, see the screenshot below.
We encourage you to search on the forum where we have existing guides about the features we have.
If you say that you have never used mDNS, which explains the previous config does not contain the mDNS. It should not be the reason why it cannot print.
The reason is something else with the computer.
My dear friend.
Thank you very much.
You were absolutely right.
And that was without doing any further research.
I didn't even go to the forum.
I was very upset that accessing the printer's web address would turn it on. However, it wouldn't print.
I reset the networks and nothing.
So I decided to redo the printer driver installation process, removing and reinstalling from scratch.
And then I noticed there was an option in the drivers for connecting to the printer that gave me two options. We always want to follow the recommendation, but it's not always the answer. That's why I like to go against the rules sometimes, and it takes me a long way.
There were options for connecting to the printer through the router and connecting directly to the printer. I was going with the first option, which was the driver's recommendation. I went with the second option this time, and everything worked.
It was my own ignorance. Omada is unbeatable, as always.
My friend. Off-topic. When will we have:
1- The new, better-tuned versions of the OC200 and ER605 firmware?
2- I'm quite disappointed with the Omada market in Brazil. I see more affordable and better equipment than the ones I own outside of Brazil, but it's not available here. I'd like to have more features like IDS/IPS on my network with the product itself;
3- I don't know if I'm talking nonsense, but I find Omada's logs a bit simple. I'd like to analyze the logs in a more complete format for manual inspection. Is it possible to enable a more complete logging mode?