topic DNS failure? in Teamwork & BIMcloud

DNS failure?

Achille Pavlidis — Tue, 03 Jul 2012 09:28:40 GMT

We are recently experiencing the following problem: Even though everyone is regularly using TW and sending/receiving normaly, at one point somebody is unable to send/receive or reserve and gets an error message of "Unsuccesfull Teamwork Operation". The user appears online, but when checking the connections there seems to be a DNS error, even though the DNS is running and the server address is resolved.
The error goes on for 4-5 minutes and then the user is again able to work properly on TW, even though the DNS error is still on...

Any ideas?

Re: DNS failure?

Anonymous — Fri, 06 Jul 2012 01:22:30 GMT

had something vaguely similar...
is your bim server machine using a fixed IP?
Your ping results seem to suggest yes but the obvious questions etc.

Re: DNS failure?

Achille Pavlidis — Fri, 06 Jul 2012 07:17:07 GMT

Yes it has a fixed IP.
And all the macs on the office LAN have the serve's IP adress first on the DNS settings

Re: DNS failure?

Anonymous — Fri, 06 Jul 2012 11:17:46 GMT

Another obvious question - have you tried with firewalls and anti virus switched off?
Other than that it sounds like you might be entering 'bug' territory, sorry.

Re: DNS failure?

Achille Pavlidis — Fri, 06 Jul 2012 11:30:11 GMT

Yes tried the firewall thing. I dont have antivirus.

I was afraid Im facing a bug...

Re: DNS failure?

Laszlo Nagy — Sat, 07 Jul 2012 13:24:27 GMT

Here is the answer I got from the guys at GS HQ tech Sup:

The troubleshoot server connection dialog may not be robust enough to help
the user.

The third section in the following wiki article may be of help:
http://archicadwiki.com/Teamwork/ConnectionProblems

It is possible that the DNS service is not answering fast enough and the
timeout before retry may be the source of the delays.

Also, the issue was been entered into the bug database.

Re: DNS failure?

Tamas Eros — Fri, 13 Jul 2012 08:21:58 GMT

Dear Achille,

What is the current state of the problem? Could you achieve any improvements?
Regards,

Re: DNS failure?

Achille Pavlidis — Mon, 16 Jul 2012 06:34:45 GMT

Hi Tamas,

the problem persists as I described it. Could not make any progress.

Re: DNS failure?

Achille Pavlidis — Tue, 17 Jul 2012 08:28:47 GMT

FYI the problem appears with AC 16 too...

Re: DNS failure?

Tamas Eros — Fri, 20 Jul 2012 07:56:44 GMT

The Teamwork Communication error indicates that the discovery service of the Teamwork Server is not available for that client. The following causes are possible:

1. The client can not reach the server through port 6005 (default discovery port in the BIM Server preferences) May the port is not opened on one of the computers. You can easily check this with telnet.

2. May you have changed the discovery port in the server but did not set each clients accordingly. The same port has to be set in the Client ArchiCADs in the Work Environment on Network and Update tab.

3. Other network or network configurational error.
The communication via the discovery port uses UDP as well (besides TCP/IP) what has to be allowed on each router, server between the client and the BIM Server computer.
If the server runs on a normal OS not on a server type it can limit the number of the current TCP/IP connections to 128. Increasing this limit to 512 or 1024 could help. In case of OS X we recommend this article: http://rolande.wordpress.com/2010/12/30/performance-tuning-the-network-stack-on-mac-osx-10-6/ which gives a description how to do this.

Generally teamwork functions are independent from the discovery function so they still work when the discovery service of the server is not available.

Re: DNS failure?

Achille Pavlidis — Fri, 20 Jul 2012 10:54:14 GMT

Hi Tamas,
I checked thourogly the points you have suggested, and I found that the sockets are 512 on both the server side and the clients.
Also the BIM server is running on Mac OSX 10.6.8

As for the sockets, I saw that each client opens a lot of connections, about 12. So for 6 persons working on a TW projects we can easily reach 72 sockets, which is rather too much I think.

Anyway thanks for your involvement in solving the problem

Re: DNS failure?

nitizz — Fri, 13 Dec 2013 07:23:54 GMT

Achille wrote:
Hi Tamas,
I checked thourogly the points you have suggested, and I found that the sockets are 512 on both the server side and the clients.
Also the BIM server is running on Mac OSX 10.6.8

As for the sockets, I saw that each client opens a lot of connections, about 12. So for 6 persons working on a TW projects we can easily reach 72 sockets, which is rather too much I think.

Anyway thanks for your involvement in solving the problem

Have you manage to resolve the DNS
Me too Im having the same problem
Only DNS Failed
Please Help me
Im working on AC17

Re: DNS failure?

Achille Pavlidis — Fri, 17 Jan 2014 10:57:48 GMT

No, I haven't.

Actually we are facing right now a serious problem.
All the users appear to have DNS resolve error, but we are working normally on TW project.
The server has static IP and the address is correctly resolved by all macs. Checked nslookup and Network Utility.

However, one user went offline and could not by any means re-connect to the server. Tried everything. Delete connection files from preferences etc etc, nothing. Offline.

Then he tried joining the project as a different user, and this time he was able to join and work properly, even if he still appears to have DNS connection error...

What to do???

Re: DNS failure?

JaredBanks — Mon, 24 Mar 2014 17:14:58 GMT

did you ever solve this? Facing the same issue.

Re: DNS failure?

JaredBanks — Mon, 24 Mar 2014 17:57:23 GMT

My solution - delete all my local data and resign in. Seems to have worked. Hope that was the issue.

Re: DNS failure?

Eduardo Rolon — Mon, 24 Mar 2014 23:35:00 GMT

having the same problems.

Re: DNS failure?

Anonymous — Fri, 26 Sep 2014 09:54:46 GMT

Just installed new 18 bim server. Getting DNS error!!

Can log in to project, work for a while and then get the DNS error. Work offline for a while then no problem again. Keeps jumping on and off!! How can I solve this problem?

Working on MAC OS X 10.9.4