System crash after QuickBooks tech support

[Kenneth Brody]

On 7/17/2012 10:34 AM, daN baueR wrote:
> Fire drill over filePro is now running normally. I had to add port
> 6556 to the list of allowed ports on the server. Don't know why or how
> it got closed since filePro had been working for years. Must have been
> something the folks at QuickBooks had played with.

Why were the QuickBooks people looking at the filePro config in the first 
place?  (Your original post said "the QB tech support proceeded to muck up 
the filePro install".  Or did you mean that, in "fixing" the QB problem, 
they "mucked up" filePro as a side effect?)

> Follow up question.
> The original filePro startup script didn't include a specific
> reference to the port it just referenced the server by name. Should
> that be changed to include the port?

You could, but port 6556 is the default port number for the filePro license 
manager.

> And would I see any
> speed/performance difference if I referenced the server by IP address
> instead of name.

Perhaps a few microseconds improvement on startup, as it probably takes a 
tiny amount less time to resolve a dotted address than the name of a local 
system.  (And the name would be in the DNS cache anyway, since I presume 
that the network share uses that server name.)

[...]

-- 
Kenneth Brody