You are viewing limited content. For full access, please sign in.

Question

Question

Changing the Server Notification Port and LFAPI port without breaking the workflow subscriber

asked on February 13, 2015

I changed the server notification port and LFAPI port and the subscriber can no longer communicate with the server. Changing the ports back to default fixes the problem. The only settings I see for the monitored repositories are in the screenshot below. Is there something I need to do to allow it to work with alternate ports?

 

0 0

Answer

SELECTED ANSWER
replied on February 13, 2015 Show version history

Is there a reason why you need to change it? Development notes that the subscriber auto-detects the notification port for LFS.

0 0
replied on February 13, 2015

It is a test server and we are trying to hide it from the network while keeping it available to users who need to access it. Just changing the listening port is not enough to hide it, the other ports need to be changed also.

0 0
replied on February 13, 2015

Is the goal to make the server not show up on the repository list on the Client's start screen or when users try to attach a repository?

0 0
replied on February 13, 2015

Yes exactly but without disabling the automatic search on the client machines. We just want the server to hide and not broadcast itself.

0 0
replied on February 13, 2015

Changing the ports will not prevent the server from broadcasting itself. Setting up the registry key described in this KB article will stop it from publishing its connection point on the domain.

1 0
replied on February 13, 2015

I am unable to get that to work. I removed the prefix so it looks like this and restarted the service but a remote sever is still showing the repository when I run a repository search.

 

0 0
replied on February 13, 2015

Right, you already have a connection point published for the server. That needs to be deleted first. The lfscpcnfg utility is located in the server install directory.

Please confirm by performing the following steps:

  1. Use the lfscpcfg delete command to delete the registered SCP
  2. Use the lfscpcfg list and/or query command to confirm that the SCP is no longer present
  3. With the registry change in place, restart the Laserfiche Server service
  4. Use the lfscpcfg list and/or query command to confirm that the SCP is not registered back

On the machine you're running the Client on, you'll want to confirm that the repository was not already attached (and hence, saved in the registry).

1 0
replied on February 13, 2015

Can I do this through the Administration Console. I did try to run it via command line but I get the following access issue, even if I "Run as Administrator" although I am an administrator. I swear the security is overwhelming.

 

0 0
replied on February 16, 2015

You need to be a domain administrator. See this page for more information.

0 0
replied on February 17, 2015

awesome this worked, thanks!

0 0

Replies

You are not allowed to reply in this post.
You are not allowed to follow up in this post.

Sign in to reply to this post.