Hi all,
I am trying to use DOLS, and ance again i am requesting your help !
My problem is that when i try to sync i get the error message of the subject.
Our config is a bit intricate :
We have a domino server in a DMZ which is in its own domain (domino domain). We haven’t any account or users registred in this domain. we have just give all of our users rights to use this server from the web (http).
Thus the Notes Id of the users which DSM use to connect to the web server weren’t certified with this domain.
Have you any good advices ?
Subject: DOLS : “Connexion Refused : The name of the server you are connected is different from the one asked”
For me, this has always been an IP address resolution issue. If, for example, a user’s personal address book contains a connection doc for a server with a hard-coded IP address that happens to be assigned to a different Domino server, you’ll get that error. These connection docs often get created during initial workstation setup, and nobody ever even knows they’re there until IP addresses change.) Incorrect hosts files or DNS tables can cause this as well, and since with DOLS your problem is with web browsers, not notes clients, I’d suggest you check the IP address being handed to those browsers for that server.
Subject: RE: DOLS : “Connexion Refused : The name of the server you are connected is different from the one asked”
The ip config of the client is the following :When using the notes client, we are openning our databases on the server in our Lan. Since we are mobile users, we are always connecting this server by using our public internet adress. The firewall then redirect 1352 comunications to the domino in the lan. To perform this. we have a connection document that point the lan server to our internet adress. When we are using http, the firewall redirect the requests to the domino server wish is in the DMZ…
Do you think it can work ?
Subject: RE: DOLS : “Connexion Refused : The name of the server you are connected is different from the one asked”
You write “We haven’t any account or users registred in this domain. we have just give all of our users rights to use this server from the web.” I’m not sure what you mean by that second sentence, but:
You have to provide some way of authenticating your users. They don’t have to live in the web server’s domain; they can be authenticated via a secondary address book.
I’d recommend replicating the primary domain’s NAB over to the web server and configuring it via directory assistance. Since you can set the ACL of this secondary NAB to a default of No Access, then when web users do authenticate (via dir asst, where the server accesses the secondary NAB, not the user), they don’t need read access to it, so they can’t see anybody in it.