Domino 8.5 remote setup "Network Communications Error"

I've installed a new 8.5 server on a RH base (actually CentOS). The install was fine, but the remote setup (from a windows admin client) fails at 1% (after all the configuration data has been entered) with a 'Network Communications Error'.

That's all the information it gives, no sign of any problems in the setuplog.txt or on the server console.

I can't run the setup locally as it's a hosted box and doesn't have an XServer running (I suppose I could install X, but I'd rather not have to).
I can't tell where the network error is - it's connecting to a second hosted box which is the master directory, back to the remote setup box (though that got through the configuration screens fine), or could even be a loopback problem I suppose.
Both boxes have the firewall set to allow any traffic from the other server, and from my internal network.

Nothing useful on Google or EE on the subject at all. Has anyone else come across this, or got any brilliant ideas. I'm going to try a re-install next while I wait.
setuplog.txt
LVL 3
tomsparrowAsked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Kerem ERSOYPresidentCommented:
Hi,

The notes client expects yu to make your host pingable. Just check if you can ping the host from a command line iin your windows Client. If not please add your servername and IP address to your C:\Windows\System32\drivers\etc\hosts in this format:

x.x.x.x    dominohost.example.com dominohost

After you make sure that you can ping your host or at least you see that the ping can resolve your host IP from the name (because some firewalls disable ping) make sure that you domino server is not blocking traffic to the port 1352. To check this just list the currently active firewall rules on your domino box with such a command

service iptables status

make sure that it lists domino ports between allowed ports such as:
.
x    ACCEPT     tcp  --  0.0.0.0/0            0.0.0.0/0           state NEW tcp dpt:1352
.

Where X stands the rule number on your list of iptables rules.
0
tomsparrowAuthor Commented:
Networking is all set up and correct at both ends - I can make the connection to the new server, and work my way through the setup screens, it's just when it actually tries to start the setup that it falls over.

All traffic is allowed from our internal network to the external box, so that covers 1352.

I've just tried a silent setup, and got a bit more info from the log out of that - it looks like it's the connection to the current Notes server that's being refused. I've had that before even on local networks, but it's always been at 20% and because the new server is not permitted to access the existing one (not in LocalDomainServers) but neither of those is true in this case. I'm going to check the access controls on the current server and see if that helps.

Thanks,
Tom
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Sjef BosmanGroupware ConsultantCommented:
0
Powerful Yet Easy-to-Use Network Monitoring

Identify excessive bandwidth utilization or unexpected application traffic with SolarWinds Bandwidth Analyzer Pack.

tomsparrowAuthor Commented:
OK, that helped - because it was a single server I'd never bothered to set up access for anything else. Stupid. Would be nice to have an error message somewhere that meant something (as usual, Lotus)

Getting a different error now:
"Directory Assistance failed opening Primary Domino Directory names.nsf, error: File does not exist"

But it is running something...
0
Sjef BosmanGroupware ConsultantCommented:
Shoot... Didn't refresh before I posted...
0
tomsparrowAuthor Commented:
Sjef - just did, though instructions on how to do that are a lot more common than on how to create the config file for it...
0
tomsparrowAuthor Commented:
and bingo - not sure what the names.nsf message was about, but the server is starting at least now.
0
Sjef BosmanGroupware ConsultantCommented:
DirAss usually isn't important when starting a new server. You could disable the task in notes.ini, and enable it again later.
0
Sjef BosmanGroupware ConsultantCommented:
You solved the issue in less than an hour! Wouldn't that qualify us as excellent bouncers...?  LOL
0
tomsparrowAuthor Commented:
You'll definately be on the doors at my next gig.
0
Sjef BosmanGroupware ConsultantCommented:
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Lotus IBM

From novice to tech pro — start learning today.