[natty] can't connect to groupwise server: Servname not supported for ai_socktype

Bug #708308 reported by henk on 2011-01-26
40
This bug affects 8 people
Affects Status Importance Assigned to Milestone
Evolution
Won't Fix
Medium
evolution (Ubuntu)
Undecided
Unassigned

Bug Description

Binary package hint: evolution

When I try to connect to a Novell groupwise server using ssl encryption I get the following error message:

Error while Scanning folders in 'GroupWise server <groupwise server>'.

Host lookup failed: <groupwise server>: Servname not supported for ai_socktype

I only have problems with the mail, the calendar is working fine..

I don't have this problem with the same configuration on maverick

lsb_release -rd:
Description: Ubuntu natty (development branch)
Release: 11.04

evolution:
  Installed: 2.32.1-0ubuntu3
  Candidate: 2.32.1-0ubuntu3
  Version table:
 *** 2.32.1-0ubuntu3 0
        500 http://nl.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
        100 /var/lib/dpkg/status
libegroupwise1.2-13:
  Installed: 2.32.1-0ubuntu4
  Candidate: 2.32.1-0ubuntu4
  Version table:
 *** 2.32.1-0ubuntu4 0
        500 http://nl.archive.ubuntu.com/ubuntu/ natty/main amd64 Packages
        100 /var/lib/dpkg/status

Ron Lusk (luskwater) wrote :

Affects me using Natty alpha 3 and Evolution 2.32.2

The error message seems to indicate you entered "groupwise server" where the account configuration dialog was expecting a server name or IP address. Please revise your settings and confirm that it works properly if the settings are adjusted.

Thanks!

Changed in evolution (Ubuntu):
status: New → Incomplete
henk (henk1234) wrote :

I actually entered the name of the server, I just altered the error message to hide my server name and IP.

Changed in evolution (Ubuntu):
status: Incomplete → Confirmed
Changed in evolution:
importance: Unknown → Medium
status: Unknown → New
Hari Gangadharan (hari-g) wrote :

I could solve this by adding entries in the /etc/services

For me groupwise was connecting to 1677 port. Hence I added the following two entries and everything became OK:
groupwise 1677/tcp
groupwise 1677/udp

In Natty, there seems to be a restriction for evolution to go against ports that are not defined in /etc/services. I hope you can also solve it by adding the above two entries (change the port number if your groupwise server is in a different port).

Hope this helps.

Hari Gangadharan

henk (henk1234) wrote :

I can confirm that adding the two lines to /etc/services solves the problem.

Bongoman (bongoman) wrote :

confirmed too

Dan Elder (dantheelder) wrote :

I can confirm the same problem although the workaround is effective. I'm not sure why it needs these definitions though, the Groupwise SOAP access is over port 7191 and nothing uses the native Groupwise ports (1677) that I know of.

Chadarius (csutton-chadarius) wrote :

I can confirm that adding the /etc/services solves the problem as well. So is this just a packaging issue?

Daniel Crosio (daniel-crosio) wrote :

Hi all,

I have the same problem but the solution dont work.
I added 1677 tcp and udp and 7191 tcp and udp.
any idea?

Thxz

Changed in evolution:
status: New → Won't Fix
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.