• State Not Answered
  • Replies replies
    9
  • Subscribers subscribers
    15
  • Views views
    549
  • Users 0 members are here
  • Locked Locked
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

GMS18 - Device State -- Never Connected --

tdebeer
HI All,

OK my new gms18 sever .... ALL LOOKS perfect, dsapp is happy with every little thing ... i have tried secure 443 and port 80 for the devices, nothing else on server is listening on port 443 or port 80 .. is the same for both . for internal testing (awaiting for firewall guys to open from public), i setup my local laptop (done this before aswell before i go production with the server) to test in the meantime.

1. I can setup the account ( with MS mail app (yes gms is set to allow ALL apps, including outlook and outlook mobile , it authenticates 100% , and says it is going to fetch my mail... but nothing ever reaches the account .. on the mobile server side .. it still says no devices ever connected yet i have autheticated with the device ..shouldn’t that already register as "device connected" ?..(only me and my other 2 admin added as users for now to test).

2. i have re-installed now about 3 of 4 times .. nothing?...

3. I did changed the name of the server but re-inslled about 3 x tmes after that .. and the name in hosts = lfsx14 lfsx14.nwpg.gov.za and in hostname = lfsx14.nwpg.gov.za anywhere else it need to be changed?..maybe this is the issue something on the name of the server?.

Kind Regards,

Thys
Parents
  • 0  
    In article <tdebeer.8jf8fb@no-mx.forums.microfocus.com>, Tdebeer wrote:
    > I did changed the name of the server

    as long as it is correct and remains the same as you proceed with the
    install should be good, but what is correct can hang us up.
    The full name needs to be how the devices see it and they have to
    resolve to it.
    So lfsx14.nwpg.gov.za needs to be
    A) directly resolvable by the device(s) (I see this isn't public yet)
    B) needs to match the certificates that are tied to a root CA known by
    the device. I.e. Can't be getting any cert errors when you point a
    browser to https://lfsx14.nwpg.gov.za but should get a 403 -
    Forbidden: Access is denied.
    In the early days we didn't need to be that specific, but now many
    modern devices do insist on flawless SSL/TLS without any 'errors' such
    as self minted certs.

    Check /var/log/datasync/mobility-agent.log for any activity.

    It might be worth doing a packet capture from either/both end points to
    see what is happening. To see such basics as is your 'device' actually
    getting to the GMS box and how is the SSL negotiation going.


    Andy of
    http://KonecnyConsulting.ca in Toronto
    Knowledge Partner
    http://forums.novell.com/member.php/75037-konecnya
    If you find a post helpful and are logged in the Web interface, please
    show your appreciation by clicking on the star below. Thanks!
    GMS troubleshooting tips at
    http://www.konecnyad.ca/andyk/gwmobility.htm


    ________________________

    Andy of KonecnyConsulting.ca in Toronto
    Please use the "Like" and/or "Verified Answers" as appropriate as that helps us all.

  • 0 in reply to   
    HI Andy,
    Thanx fo the reply.
    A. yes it can resolve fine, i do actually connect and authenticate (testing form internal laptop on the internal network for now)
    B. Yip i get only the 403 error, so cert looks good..
    c. even if i set it to port 80 and not 443 (certificate) it still the same result, when setup the device, my account authenticates, and says it going to "fetch my email" (MS mail app)

    lfsx14 is just the server name .. the actual dns name the users would use is nvmobile2.nwpg.gov.za .. but tried the nams as lfx14.nwpg.gov.za this morning as well..same result?
  • 0 in reply to 
    Hi Thys,

    I think that might be your problem (A), you're testing has been resolving against your internal DNS servers. If I search public DNS for your server (nvmobile2.nwpg.gov.za) I get a "Non-existent domain" response. So when your mobile phones are using the public DNS they can't resolve your server DNS entry so never hit it.

    Mark.
  • 0 in reply to 
    HI Mark,

    Thanks, but the thing is i only test internal with a laptop (with ms mail app) ..tested like this before before i went live with previous servers (public for form outside) .. hitting the mobile server is fine from the laptop, web browser etc ... i even in the mail app authenticate so it's gotta hit the mobile server right?

    Thys
  • 0 in reply to 
    Hi Thys,

    Set your GMS log level to DEBUG. Try a sync on a device. Then take a close look at the mobility-agent.log file in /var/log/datasync/connectors/ for a connection from the device. Let us know what you see.

    Cheers,
  • 0 in reply to 
    HI Everybody,

    Well it seems the windows mail app, was the issue, took my tablet, set it op on oly wifi an only internal, with no link out, and connected to the mobility server "form inside" as if it was a pc with active-sync client, and it worked, something with that windows mail app it seems, wow and this after re-installing gms about 4 times, and then a complete new server again from scratch ... again shows you never trust what a m$ device tells you..... thanks for everybodies suggestions..

    Cheers
Reply
  • 0 in reply to 
    HI Everybody,

    Well it seems the windows mail app, was the issue, took my tablet, set it op on oly wifi an only internal, with no link out, and connected to the mobility server "form inside" as if it was a pc with active-sync client, and it worked, something with that windows mail app it seems, wow and this after re-installing gms about 4 times, and then a complete new server again from scratch ... again shows you never trust what a m$ device tells you..... thanks for everybodies suggestions..

    Cheers
Children

Resources

Support
Documentation
Learning Services
Partner Programs
Privacy
Compliance
Help
Company
Privacy Policy
Terms of Use
Cookies Preferences
Accessibility
Anti-Slavery Statement
Support
Contact Us
Careers
Code of Business Conduct and Ethics
The opinions expressed above are the personal opinions of the authors, not of OpenText. By using this site, you accept the Terms of Use. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.), Hewlett Packard Enterprise Company, or Micro Focus. As of January 31, 2023, the Material is now offered by OpenText, a separately owned and operated company. Any reference to the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks is historical in nature and the HP, Hewlett Packard Enterprise/HPE, and Micro Focus marks are the property of their respective owners.