intranet 192.168.1.xxx could be accessible with port forwarding from a router
but it can get complicated.
'password protected' depends on how it's is set up --and why is that necessary. http auth is pretty useless to actually protect anything today
This can be as simple as a whitelisting requirement. As Graybeard says, it will be complicated as you would need the DP Manager, or comparable, create the whitelisting (if it is still done that way).
Welcome to Our Community
Wanting to join the rest of our members? Feel free to sign up today.
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.
Attention: "role based name" email prefixes such as support, webmaster, info, contact, forum, service, affiliate, admin, traffic, partners, marketing, etc., for our member accounts are not permitted. They are acceptable for a vendor listing, but not for the member email. This is due to bulk email processors scrubbing them for delivery due to extremely high bounce rates. Please apply for membership using a personalized email prefix. Something like bob@xxxxx.com.
If we discover you signed up with a role based name we will give you only one message to change it. After 3 days your account will be removed if the email is not changed.