Hi,
I have installed multiple NAV Services with Port Sharing. (LIVE, TEST with Windows Auth. and LIVE, TEST with NavUserPassword)
As example:
AD Domain: mydomain.local
NAV Service: navserv@mydomain.local
Services:
(Windows Auth)
LIVE
TEST
(NavUserPassword)
LIVEU
TESTU
Alle Services are working fine but ...
I added a new DNS Zone example.com for which we have a wildcard certificate which is already configured for the services. I created an A-Record "NAV" which holds the IP for the navserv Server. nav.example.com -> navserver@mydomain.local
When I start the service the net.tcp listener is listening for navserver@mydomain.local
Now I would like to use the external domain for the services.
When I try to access the Service from Windows Client with nav.example.com:8046/navservice I get the error
" A server was not found at "net.tcp://nav.example.com:8046/nav/Service". Either the URL is incorrect or the server is currently not available.
If I change the connection string back to localhost I can connect as expected.
Important things to know..
- Firewall is turned of
- Services are working with internal DNS records or even with ip
- nslookup nav.example.com is working on the server and delivers the correct ip
- ping nav.example.com is working (firewall is off)
- User is setup in nav
- Service User is setup correct ... Because all services are working with correct
- I'm testing the connection directly from the dns server where nav is installed. It's also the DC (I know ... )
-
Summary ...
localhost:8046/nav = OK
navserv.mydomain.local:8046/nav = OK
<IP>:8046/nav = OK
nav.example.com:8046/nav = NOK
ANY idea?
0
Comments
NavUserPassword is working on this.
So it seems that Windows Auth. is not working on this external domain URL.
I will keep you up to date if I can find a solution ...