Hello.-
We need to publish an internal server which demands Access in two different schedules. This schedules are applied in accordance to FROM the server is accesed. The issue here is that when the publishing rules are applied the following Alert is reported
"The server publishing rule NAME, which maps x.x.x.x:TCP to
y.y.y.y for the protocol PROTOCOL
Server, was unable to bind a socket for
the server. The server publishing rule cannot be applied.
The failure is due
to error: You were not connected because a duplicate name exists on the network.
If joining a domain, go to System in Control Panel to change the computer name
and try again. If joining a workgroup, choose another workgroup name"
A workaround to this is to change the published sockect adding an IP to the EXTERNAL Network or listening on a different port in the the publishing rule , however we would like to know if there is a better way to define distinct publishing rules which applies in different schedules for the same protocol.
Thanks in advance.
