@jhweiss
Hi,
Is it the first time that you can not log in on windows client?
Please visit our website when you can not log in. We want to make sure that the internet works.
What's the version of your system? We want to check it.
The latest version is 4.1.17. Please update to have a try.
http://version.doit.im/dl/windows.setup.4.1.17.zip
Best regards,
Doit.im Team
The web client works fine.
Log attached.
Thanks,,
Jeff
-
06/19/2014 02:20#1PRO
-
06/26/2014 15:36#3PRO
@wendy_only
I am using 4.17 already.
Are there non-standard network ports in use for the app but not the web version?
Thanks,
Jeff -
06/27/2014 03:14#4PRO
@jhweiss
Hi,
I want to know if you can visit our server when I ask you to visit our website.
Please try to ping api.doit.im which is the address the windows app visit. Check the result and let me know.
BTW,do you use proxy?
Best regards,
Doit.im Team
-
12/08/2014 06:47#5PRO
Hi I am seeing the same problems as Jeff. Previously I was able to connect using the Windows client when running on Win 7. But when my machine was re-imaged to Win 8 the client stopped working.
Ping from the command line works:
Pinging api.doit.im [54.248.223.214] with 32 bytes of data:
Reply from 54.248.223.214: bytes=32 time=116ms TTL=38 etc...
Logging into the web client works.
Any suggestions on what the problem and fix might be? -
12/08/2014 08:27#6PRO
This is a private comment.
-
12/08/2014 22:17#7PRO
Thanks for the update. Unfortunately seems to be the same result. Log file attached.
I pinged the three hostnames you requested I add to the hosts file. doit.im and api.doit.im were routed 54.248.223.214. Where i.doitim.com went to 211.155.229.2 prior to the host file change. Now it goes to the same address as the others.
Pinging i.doitim.com [211.155.229.2] with 32 bytes of data:
Reply from 211.155.229.2: bytes=32 time=332ms TTL=30