Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
Send Invite Cancel
Solved
Go to Solution
Link copied. Please paste this link to share this article on your social media post.
We have a public LAN and private LAN configuration in DCE 7.9.2.
For all these tests the DCE client is connected to the PRIVATE LAN whith an IP like 192.168.13.200 or any other available.
The private LAN is divided into 2 locations (PZ and AS) linked by optical fiber configured as a LAN EXTENTION. The DCE is installed in the AS location and the devices of PZ cannot be accessed their web pages from DCE by double clicking on its.
The port and protocols are fine as their user ID and password.
Also these devices on PZ location are visible and without errors in DCE via SNMP, only access to the web page fails for some.
I attach images of the errors.
DCE Public LAN
DCE private LAN
Accesing a device from DCE with http located on AS location (ok)
Accessing a device fron DCE on PZ location with http (fail)
Accessing a device from DCE with https located con AS on operating system browser.
Access a device from DCE on PZ location using https
(note de url that sais /privateproxy/null/.
Accepted Solutions
Link copied. Please paste this link to share this article on your social media post.
Hello. I finally found the error.
If DHCP has ever been configured in the "private network" tab, then even if this is disabled, it affects the network configuration. It is clear that it is a bug. Enabling DHCP again and changing the mask to 255.255.240.0 and deactivating it again, the problem was corrected.
Anyway, the DHCP mask was changed back to 255.255.248.0 but it no longer affects
Link copied. Please paste this link to share this article on your social media post.
Hello. I finally found the error.
If DHCP has ever been configured in the "private network" tab, then even if this is disabled, it affects the network configuration. It is clear that it is a bug. Enabling DHCP again and changing the mask to 255.255.240.0 and deactivating it again, the problem was corrected.
Anyway, the DHCP mask was changed back to 255.255.248.0 but it no longer affects
Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.