Gethostbyaddr() and reverse DNS name do not match

So we updated to 10.4.6 on our server... and now none of the clients can connect...
Our DNS and reverse DNS (done by the university IT group) have caps in them... but all the home directories for users are lower case...
How can I fix this - short of entering all home directory info in by hand? Oh - suggesting that the IT group change the DNS is not helpful as it will not happen.
  Mac OS X (10.4.6)   Server

A summary - Here's the situation:
1. I have a 10.4 server running on a G5 tower.
2. The DNS is operated by the university IT group and our reverse DNS is mixed case... asked and they're not going to change it.
3. 10.4.6 introduced some funky stuff with FQDN, DNS and case sensitivity issues.
So... before I changed anything after the 10.4.6 update... users couldn't log in because it couldn't get their home directories...
The automounter would be looking for:
/Network/Servers/servername.Psychology.McMaster.CA/Users/username
While if you looked in /Network/Servers/ you will see:
/Network/Servers/servername.psychology.mcmaster.ca
(note the case)
Alright - moving on:
4. Tried changing hostconfig HOSTNAME - only worked on local server (and you're not supposed to do this anymore).
5. Used changeip same IP address, lower-case name to mixed case name... now users could log in.... glory!
6. Argh... they can log in, but can only intermittently actually get their home directories... seriously. You log in, see your desktop and flash it's gone... clicking on your home directory or desktop in finder gets you 'The volume for "Desktop" cannot be found'... doing "cd ~" and then "ls" from a terminal window sometimes gets you your directory, a partial directory or an error... and even then the ownership maybe the user or root...
7. Looking in the logs we see:
May 25 14:48:26 client kernel[0]: AFP_VFS afpfs_unmount: /private/Network/Servers/servername.psychology.mcmaster.ca/Users, flags 524288, pid 490
May 25 14:48:26 client kernel[0]: AFP_VFS afpfs_MountAFPVolume: GetVolParms failed 0x16
May 25 14:48:26 client automount[490]: Can't mount servername.Psychology.McMaster.CA:/Users on /private/Network/Servers/servername.Psychology.McMaster.CA/Users: Invalid argument (22)
May 25 14:48:26 client automount[490]: Attempt to mount /automount/Servers/servername.Psychology.McMaster.CA/Users returned 22 (Invalid argument)
May 25 14:48:26 client automount[489]: Can't mount servername.Psychology.McMaster.CA:/Users on /private/Network/Servers/servername.Psychology.McMaster.CA/Users: Invalid argument (22)
(server and client names changed to protect the guilty).
I'm stumped... and it's to the point that the owner of said server (a staunch apple supporter) is asking if I can replace the server with a Linux box with LDAP/AFP/SMB...
Any help here?

Similar Messages

  • Still cannot resolve "gethostbyaddr() and reverse DNS name" warnings.

    "Mar 15 11:02:48 xs1 servermgrd: servermgr_dns: gethostbyaddr() and reverse DNS name do not match (xs1.dept.school.edu != xs1.dept.School.EDU), various services may not function properly - use changeip to repair and/or correct DNS"
    I have two xserves, both of which keep generating the same warnings, ad nauseam, in /var/log/system.log and having followed all suggestions and instructions in discussions, technical notes, afp548.com, and from other sysadmin's I still cannot stop them. There do not seem to be any services affected, or at least not in an overt manner.
    Both xserves run slightly different services: (xs1) AFP, Firewall, NetBoot, NFS, Open Directory (slave), Print and Web; and (xs2) AFP, Firewall, Open Directory (master) and Software Update.
    On both xserves I have run the following commands/tests with correct results, yet still I get the warnings in system.log: "changeip -checkhostname" is correct, and "scutil --get HostName" is correct. The /etc/hostconfig file is correct with "HOSTNAME=-AUTOMATIC-".
    The only thing I can consider is that when setting them up, I had entered the FQDN in all lower-case, but the reverse dns is not, our domain is capitalized, and the tld is in all caps on the DNS servers. I had ages ago issued the "changeip" command as recommended in the warning, to no effect, even though "changeip -checkhostname" says it's correct.
    Where the heck to I look now? This is driving me nuts!
    RackMac1,1 & RackMac3,1   Mac OS X (10.4.8)  

    >As of 10.4.6, Apple states to never change /etc/hostconfig's HOSTNAME entry.
    Inside the little black box that Apple runs Mac OS X Server this might be good advice. However, in the real world, real servers are often outside of Apple's box (sometimes far outside) and you have to do certain things that Apple don't advise or 'support'.
    I can't tell you how many things I run on my servers that are outside the box and judging by other posts on these boards I'm not the only one. You only have to look at DNS, web and mail for starters to see that Apple's model doesn't cover everyone's needs.

  • User account name and home directory name do not match

    A month ago I bought the latest iMac and used Migration assistant to migrate all of my data on over.
    Everything went well... Except that my new iMac would not let me use my old user name. I had to create somethign else.
    So my user (admin) account name is not the same as my Home directory name. (I only have 1 user account and 1 user Home directory... they both are named differently).
    This has not caused problems, but I want to iron this out. I tried using System Preferences/Users and groups to change my user account name to match the name of my home directory name (which has my old user name)... but when I did that it said "Name not available".
    Long time Mac user but I'm not comfortable doing anything deeper without some input & advice.
    Thanks in advance!

    I enable the Root user as outlined in the Apple Way instructions...logged out and loged in as the rooot user... but I really don't want to change the name of my user directory... That's the name I want to keep as a User.
    Even logged in as a Root User...
    I tried to change my current User Name to match by directory name, but it said Name is Not Available
    I also tried to create a new User name that matches my directory name...same results Name is Not Available
    Is there a sudo entry that will change the User to match my Directory name (which I want to keep and use)?
    Thank in advance!

  • Gateway Server address and Certificate subject name do not match error on Vista client

    RD Gateway server is 2012, RD Server is 2008 R2. Client is (currently) Vista Gold (surprised me too).
    User was able to connect through the Gateway in the past, but seems to have broken around the time that we switched to a real wildcard SSL certificate. Prior to this, it was using a self issued cert.
    I'm stalling for time (and hoping this fixes it) by having the user install the Vista Service Packs. Can anyone verify if this is what's causing the issue, or if I need to look at something else?

    Hi,
    Yes, updating should fix the issue--the old client versions didn't work properly with wildcard.  I recommend you have them install the latest version of the Remote Desktop Client for Vista which is RDP 7.0 capable:
    Description of the Remote Desktop Connection 7.0 client update for Remote Desktop Services (RDS) for Windows XP SP3, Windows Vista SP1, and Windows Vista SP2
    http://support.microsoft.com/kb/969084
    -TP

  • OS X 10.4.11 Server - configured name and reverse DNS do not match / DNS

    Hi all,
    I have looked for similar posts but all seem to have different scenarios, hoping to get an answer from someone more experienced than myself before I do anything silly.
    Help much appreciated!
    Scenario:
    We run a 10.4.11 OS X Server on an XServe, hosted at an ISP. ISP provides all DNS services, incl. the reversed DNS entry.
    I am currently only running the following services (based on the display in ServerAdmin):
    AFP
    Firewall
    iChat
    Mail
    QuickTimeStreaming
    Web
    All others (incl. DNS) are grayed out. (As ISP instructed us not to add a DNS service on our box, that's "normal" according to my experiences with dedicated /co-location server hosting).
    We never used changeip after the initial setup, meaning the server's
    Current Hostname = somename.local and
    DNS Hostname = mail.ourdomainname.net
    So in system.log I find this re-occuring entry:
    Jul 8 11:41:22 somename servermgrd: servermgr_dns: configured name and reverse DNS name do not match (somename.local != mail.ourdomainname.net), various services may not function properly - use changeip to repair and/or correct DNS
    Finally, my question:
    As Mail and Web services etc. are currently running OK from what I can tell,
    1) do I HAVE to change this at all?
    2) Would it be much better / why?
    3) Could I change this using the following command
    (111.11.111.1 indicating the server's IP address)
    changeip 111.11.111.1 111.11.111.1 somename.local mail.ourdomainname.net
    4) without running a DNS server on the machine, i.e. DNS service is not required for this to work?
    5) obviously I want to be able to use Server Admin after I issue this command...
    6) can I fall back easily in case this would screw it up, or is there no risk whatsoever doing this in my case?
    THANK YOU so much for any help!

    Hi Jonas
    If port 443 is already being used on the same box as KMS then it will complain and probably not start the service? I've seen this with LDAP port 636. This is when Kerio is installed on a server configured as an OD Master. Clearly the port can't be used by both servers.
    It might be easier to change the port your sites are currently using to something else? Although don't do anything yet. Pose the question to Kerio Support and see what advice they offer.
    Yes moving the mail to a local folder on the mail client will do it.
    Is Kerio going on the same box? If its a different box (presumably different IP address?) Then what you can do is to port forward to the new server's IP address instead of disabling it. This way while you are bringing the new server on line users can still send mail right up until the time you give instructions on changing their inbound/outbound mail server details. Of course they won't be able to receive but if you time it right they may not even get an error message? Depends on what their schedules are.
    If it was me I would choose IMAP every time. As the mail admin you have full control and a central location for easy backup. KMS has a built in archiving feature that makes this a simple process. This is an easier option than going round individual client machines and making sure mail held locally in POP accounts are backed up. Besides there is always someone who falls through the loop and I'm not taking into account drive failures. It makes good sense anyway as there is talk of legislation being introduced to make this a requirement for businesses who run their own mail servers. This is certainly true for certain parts of the US and what usually happens there is generally taken up in the UK and most parts of Europe.
    Kerio's WebMail Client means users don't even have to have their own computer. Just as long as they have access to one that has access to the internet they can send/receive mail. No need for dedicated mail applications such as Apple Mail, Thunderbird, Entourage etc. How mail is uses remains consistent for all users.
    Yes. I did this not so long ago with Leopard's built in Mail Server. I sent an e-mail defining a time when no inbound mail would be received. Disabled port forwarding for SMTP port 25 and approx 30 minutes after that another mail stating no outbound mail should be sent. Once everything was swopped over (we were changing from a G4 10.4 server to a G5 10.5 Server) port 25 was enabled, new server brought online and everyone was mailing again with no appreciable downtime.
    These boxes were to have the same IP address hence the slightly different approach.
    Does this help?
    Tony

  • How do I add a computer when the ip and dns address do not match?

    I am using ARD to connect to a few computers at a remote site. The site has a Static IP, as well as each machine on the local network. One of the machines works fine (a Mac Mini running ARD 3.6), but that was set up a while ago, and any other machines (running ARD 3.6.2) I try to add will not work.
    Basically, I want to add a machine with an IP address of the location (ex. 50.50.120.181), and the DNS name of the computer on the local network (ex. 192-168-1-21.lightspeed.stlsmo.sbcglobal.net). This is how the Mac Mini is set up and works. However, every time I try to change the DNS name, it changes the IP address to match (192.168.1.21). Since I'm connecting remotely, that doesn't work. If I try to change back the IP address, it just reverts it right back.
    How do I get ARD to stick with the IP address I tell it to??

    Open System Preferences
    Click on Accounts
    Click on the padlock and enter password
    Click on login options
    There you should see an option to disable "automatic login". You should also notice some other options there that you may or may not want. They should be pretty self explanatory.
    The Security panel has an option to require password after sleep or the screen saver is invoked if you need it.
    -KeithP

  • How to stop OS X from retrieving reverse DNS name ?!

    Hello guys,
    I have a small problem that's very annoying. I manage a couple dozen Macs at work via ARD. All Macs are up to date and so is ARD.
    Recently i started to notice something bizzare in ARD, meaning that from time to time a couple of Macs that were passed over from an ex employee to another current employee, behaved erradic in ARD. Sometimes they appear offline, sometimes they dissaper entirely (also in Scanner), BUT most of the times they appear with incorrect DNS name (ex DNS name from the ex employee or even duplicates DNS names)
    I attached a pic in which you can clearly see what i'm all about.
    I tried different situations and config mods, and i almost nailed it when i changed the DHCP DNS settings from the router. Currently the router LAN DNS settings points to the local server (ie: 10.0.1.2) which has DNS enabled and then to the public DNS. If i switch the entires, then the DNS names appear correctly in ARD, but if i do that i also loose the iChat service which is dependent of that entry.
    SO i think the best way is to figure out a way to stop OS X from retrieveing reverse DNS names. Is this possible?

    I've have this issue too.  This thread may be helpful:
    https://discussions.apple.com/thread/4190442
    Most of our computers have static IP addresses assigned, so it is just some laptops that receive DHCP that seem to get confused in ARD sometimes.  As in your case, the computers themselves never have an issue - it is just ARD that gets mixed messages.  It also never seems to affect ARD, it just displays incorrectly. While I'm not entirely convinced this is fixable, I took the advice of the thread above and when it gets really bad, I simply go to "All Computers" and delete everything out.  Then I quit and reopen ARD and then from the Scanner, I re-add the computers and re-organize them.  We only have about 30 computers, so it goes quick when they are all turned on.  They seem to stay pretty organized for a while... and then the cycle begins again.

  • Error: Missing SRV record at DNS server - [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]

    in an attempt to transfer FSMO roles to the 2012r2 DC the first thing I ran was dcdiag /e /c /v and after correcting some minor errors, I came upon this one in the DNS portion where a SRV record is missing and I have no idea how to fix/remove this. there's
    only two DCs, 200.5 and 200.6 where the former is a Hyper-V VM running 2012r2 and the latter is a physical 2003r2 machine. I was able to successfully raise the levels to 2003 and join the 2012r2 DC. this missing SRV record does not look fatal and only warrants
    a warning from dcdiag, however I would like to fix this so there's no trouble down the road. I've tried ipconfig /registerdns, but no dice. here is the message I'm concerned about:
                        Error:
                        Missing SRV record at DNS server 192.168.200.5:
                        _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                        [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
    the bottom portion of the DNS section that contains this message is in the RReg section and is as follows:
                  TEST: Dynamic update (Dyn)
                     Test record dcdiag-test-record added successfully in zone cmedia.local
                     Test record dcdiag-test-record deleted successfully in zone cmedia.local
                  TEST: Records registration (RReg)
                     Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
                        Matching CNAME record found at DNS server 192.168.200.5:
                        a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
                        Matching A record found at DNS server 192.168.200.5:
                        CM-DC1-HV-NYC01.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.cmedia.local
                        Error:
                        Missing SRV record at DNS server 192.168.200.5:
                        _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                        [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._tcp.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._tcp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._udp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kpasswd._tcp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.gc._msdcs.cmedia.local
                        Matching A record found at DNS server 192.168.200.5:
                        gc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.5:
                        _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                        Matching CNAME record found at DNS server 192.168.200.6:
                        a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
                        Matching A record found at DNS server 192.168.200.6:
                        CM-DC1-HV-NYC01.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.cmedia.local
                        Error:
                        Missing SRV record at DNS server 192.168.200.6:
                        _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                        [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._tcp.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._tcp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._udp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kpasswd._tcp.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.gc._msdcs.cmedia.local
                        Matching A record found at DNS server 192.168.200.6:
                        gc._msdcs.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                        Matching  SRV record found at DNS server 192.168.200.6:
                        _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                  Warning: Record Registrations not found in some network adapters

    Hi Ace Fekay, thank you for your help. I hope you're still with me despite my lack of responding. I needed time to move the VPN server from the DC to a separate VM and then following your instructions to disable WINS Proxy and IP routing. Some of the delay
    was when I had to restart the 2003r2 server after disabling those two items since that cause DNS queries to the Internet to go unresolved with only the 2012r2 server. That's been corrected, but running dcdiag /c /e /v still gives some DNS problems. Here's
    the latest run of that...
          Starting test: DNS
             DNS Tests are running and not hung. Please wait a few minutes...
                   Starting test: DNS
                      See DNS test in enterprise tests section for results
                      ......................... CM-DC-NY01 passed test DNS
             See DNS test in enterprise tests section for results
             ......................... CM-DC1-NY01 passed test DNS
       Running partition tests on : ForestDnsZones
          Starting test: CheckSDRefDom
             ......................... ForestDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... ForestDnsZones passed test CrossRefValidation
       Running partition tests on : DomainDnsZones
          Starting test: CheckSDRefDom
             ......................... DomainDnsZones passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... DomainDnsZones passed test CrossRefValidation
       Running partition tests on : Schema
          Starting test: CheckSDRefDom
             ......................... Schema passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Schema passed test CrossRefValidation
       Running partition tests on : Configuration
          Starting test: CheckSDRefDom
             ......................... Configuration passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... Configuration passed test CrossRefValidation
       Running partition tests on : cmedia
          Starting test: CheckSDRefDom
             ......................... cmedia passed test CheckSDRefDom
          Starting test: CrossRefValidation
             ......................... cmedia passed test CrossRefValidation
       Running enterprise tests on : cmedia.local
          Starting test: DNS
             Test results for domain controllers:
                DC: cm-dc-NY01.cmedia.local
                Domain: cmedia.local
                   TEST: Authentication (Auth)
                      Authentication test: Successfully completed
                   TEST: Basic (Basc)
                      The OS Microsoft(R) Windows(R) Server 2003, Standard Edition (Service Pack level: 2.0) is supported.
                      NETLOGON service is running
                      kdc service is running
                      DNSCACHE service is running
                      DNS service is running
                      DC is a DNS server
                      Network adapters information:
                      Adapter [00000001] HP NC373i Multifunction Gigabit Server Adapter:
                         MAC address is 00:00:00:00:00:00
                         IP Address is static
                         IP address: 192.168.200.6
                         DNS servers:
                            192.168.200.6 (cm-dc-NY01.cmedia.local.) [Valid]
                            192.168.200.5 (CM-DC1-NY01) [Valid]
                      The A host record(s) for this DC was found
                      The SOA record for the Active Directory zone was found
                      The Active Directory zone on this DC/DNS server was found primary
                      Root zone on this DC/DNS server was not found
                   TEST: Forwarders/Root hints (Forw)
                      Recursion is enabled
                      Forwarders are not configured on this DNS server
                      Root hint Information:
                         Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
                         Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
                         Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
                         Name: b.root-servers.net. IP: 2001:500:84::b [Invalid (unreachable)]
                         Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
                         Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unreachable)]
                         Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
                         Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
                         Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
                         Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
                         Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
                         Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
                         Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
                         Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
                         Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
                         Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
                         Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
                         Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 198.32.64.12 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
                         Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
                   TEST: Delegations (Del)
                      Delegation information for the zone: cmedia.local.
                         Delegated domain name: _msdcs.cmedia.local.
                            DNS server: cm-dc-NY01.cmedia.local. IP:192.168.200.6 [Valid]
                   TEST: Dynamic update (Dyn)
                      Test record dcdiag-test-record added successfully in zone cmedia.local
                      Test record dcdiag-test-record deleted successfully in zone cmedia.local
                   TEST: Records registration (RReg)
                      Network Adapter [00000001] HP NC373i Multifunction Gigabit Server Adapter:
                         Matching CNAME record found at DNS server 192.168.200.6:
                         406b42db-de80-4d11-bc18-c68074007a76._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.6:
                         cm-dc-NY01.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.cmedia.local
                         Error:
                         Missing SRV record at DNS server 192.168.200.6:
                         _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                         [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._udp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kpasswd._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.gc._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.6:
                         gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.pdc._msdcs.cmedia.local
                         Matching CNAME record found at DNS server 192.168.200.5:
                         406b42db-de80-4d11-bc18-c68074007a76._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.5:
                         cm-dc-NY01.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.cmedia.local
                         Error:
                         Missing SRV record at DNS server 192.168.200.5:
                         _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                         [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._udp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kpasswd._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.gc._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.5:
                         gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.pdc._msdcs.cmedia.local
                   Warning: Record Registrations not found in some network adapters
                DC: CM-DC1-NY01.cmedia.local
                Domain: cmedia.local
                   TEST: Authentication (Auth)
                      Authentication test: Successfully completed
                   TEST: Basic (Basc)
                      The OS Microsoft Windows Server 2012 Standard (Service Pack level: 0.0) is supported.
                      NETLOGON service is running
                      kdc service is running
                      DNSCACHE service is running
                      DNS service is running
                      DC is a DNS server
                      Network adapters information:
                      Adapter [00000010] Microsoft Hyper-V Network Adapter:
                         MAC address is 00:00:00:00:00:00
                         IP Address is static
                         IP address: 192.168.200.5, 0000::0000:0000:0000:0000
                         DNS servers:
                            192.168.200.5 (CM-DC1-NY01) [Valid]
                            192.168.200.6 (cm-dc-NY01.cmedia.local.) [Valid]
                      The A host record(s) for this DC was found
                      The SOA record for the Active Directory zone was found
                      The Active Directory zone on this DC/DNS server was found primary
                      Root zone on this DC/DNS server was not found
                   TEST: Forwarders/Root hints (Forw)
                      Recursion is enabled
                      Forwarders are not configured on this DNS server
                      Root hint Information:
                         Name: a.root-servers.net. IP: 198.41.0.4 [Valid]
                         Name: a.root-servers.net. IP: 2001:503:ba3e::2:30 [Invalid (unreachable)]
                         Name: b.root-servers.net. IP: 128.9.0.107 [Invalid (unreachable)]
                         Name: b.root-servers.net. IP: 192.228.79.201 [Valid]
                         Name: b.root-servers.net. IP: 2001:500:84::b [Invalid (unreachable)]
                         Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
                         Name: c.root-servers.net. IP: 2001:500:2::c [Invalid (unreachable)]
                         Name: d.root-servers.net. IP: 128.8.10.90 [Invalid (unreachable)]
                         Name: d.root-servers.net. IP: 199.7.91.13 [Valid]
                         Name: d.root-servers.net. IP: 2001:500:2d::d [Invalid (unreachable)]
                         Name: e.root-servers.net. IP: 192.203.230.10 [Valid]
                         Name: f.root-servers.net. IP: 192.5.5.241 [Valid]
                         Name: f.root-servers.net. IP: 2001:500:2f::f [Invalid (unreachable)]
                         Name: g.root-servers.net. IP: 192.112.36.4 [Valid]
                         Name: h.root-servers.net. IP: 128.63.2.53 [Valid]
                         Name: h.root-servers.net. IP: 2001:500:1::803f:235 [Invalid (unreachable)]
                         Name: i.root-servers.net. IP: 192.36.148.17 [Valid]
                         Name: i.root-servers.net. IP: 2001:7fe::53 [Invalid (unreachable)]
                         Name: j.root-servers.net. IP: 192.58.128.30 [Valid]
                         Name: j.root-servers.net. IP: 2001:503:c27::2:30 [Invalid (unreachable)]
                         Name: k.root-servers.net. IP: 193.0.14.129 [Valid]
                         Name: k.root-servers.net. IP: 2001:7fd::1 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 198.32.64.12 [Invalid (unreachable)]
                         Name: l.root-servers.net. IP: 199.7.83.42 [Valid]
                         Name: l.root-servers.net. IP: 2001:500:3::42 [Invalid (unreachable)]
                         Name: m.root-servers.net. IP: 2001:dc3::35 [Invalid (unreachable)]
                         Name: m.root-servers.net. IP: 202.12.27.33 [Valid]
                   TEST: Delegations (Del)
                      Delegation information for the zone: cmedia.local.
                         Delegated domain name: _msdcs.cmedia.local.
                            DNS server: cm-dc-NY01.cmedia.local. IP:192.168.200.6 [Valid]
                   TEST: Dynamic update (Dyn)
                      Test record dcdiag-test-record added successfully in zone cmedia.local
                      Test record dcdiag-test-record deleted successfully in zone cmedia.local
                   TEST: Records registration (RReg)
                      Network Adapter [00000010] Microsoft Hyper-V Network Adapter:
                         Matching CNAME record found at DNS server 192.168.200.5:
                         a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.5:
                         CM-DC1-NY01.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.cmedia.local
                         Error:
                         Missing SRV record at DNS server 192.168.200.5:
                         _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                         [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._udp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kpasswd._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.gc._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.5:
                         gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.5:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                         Matching CNAME record found at DNS server 192.168.200.6:
                         a29d12f1-2869-44bf-8e43-adf7ddf33865._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.6:
                         CM-DC1-NY01.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.cmedia.local
                         Error:
                         Missing SRV record at DNS server 192.168.200.6:
                         _ldap._tcp.9a5f3c17-e7ac-48f7-ab42-bf1ea621a6f5.domains._msdcs.cmedia.local
                         [Error details: 9003 (Type: Win32 - Description: DNS name does not exist.)]
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._udp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kpasswd._tcp.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _kerberos._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.gc._msdcs.cmedia.local
                         Matching A record found at DNS server 192.168.200.6:
                         gc._msdcs.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _gc._tcp.Default-First-Site-Name._sites.cmedia.local
                         Matching  SRV record found at DNS server 192.168.200.6:
                         _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.cmedia.local
                   Warning: Record Registrations not found in some network adapters
             Summary of test results for DNS servers used by the above domain controllers:
                DNS server: 198.32.64.12 (l.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 198.32.64.12               [Err
    or details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:500:1::803f:235 (h.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:1::803f:235               [Error details: 1460 (Type: Win32 - Description: This operation ret
    urned because the timeout period expired.)]
                DNS server: 2001:500:2::c (c.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:2::c               [Error details: 1460 (Type: Win32 - Description: This operation returned b
    ecause the timeout period expired.)]
                DNS server: 2001:500:2d::d (d.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:2d::d               [Error details: 1460 (Type: Win32 - Description: This operation returned
    because the timeout period expired.)]
                DNS server: 2001:500:84::b (b.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:84::b               [Error details: 1460 (Type: Win32 - Description: This operation returned
    because the timeout period expired.)]
                DNS server: 2001:503:ba3e::2:30 (a.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:503:ba3e::2:30               [Error details: 1460 (Type: Win32 - Description: This operation retu
    rned because the timeout period expired.)]
                DNS server: 2001:503:c27::2:30 (j.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:503:c27::2:30               [Error details: 1460 (Type: Win32 - Description: This operation retur
    ned because the timeout period expired.)]
                DNS server: 2001:7fd::1 (k.root-servers.net.)
                   2 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:7fd::1               [Error details: 1460 (Type: Win32 - Description: This operation returned bec
    ause the timeout period expired.)]
                DNS server: 128.8.10.90 (d.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.8.10.90               [Erro
    r details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 128.9.0.107 (b.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.127.in-addr.arpa. failed on the DNS server 128.9.0.107               [Erro
    r details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
                DNS server: 2001:500:2f::f (f.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:2f::f               [Error details: 1460 (Type: Win32 - Description: This operation returned
    because the timeout period expired.)]
                DNS server: 2001:500:3::42 (l.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:500:3::42               [Error details: 1460 (Type: Win32 - Description: This operation returned
    because the timeout period expired.)]
                DNS server: 2001:7fe::53 (i.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:7fe::53               [Error details: 1460 (Type: Win32 - Description: This operation returned be
    cause the timeout period expired.)]
                DNS server: 2001:dc3::35 (m.root-servers.net.)
                   1 test failure on this DNS server
                   PTR record query for the 1.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.0.ip6.arpa failed
    on the DNS server 2001:dc3::35               [Error details: 1460 (Type: Win32 - Description: This operation returned be
    cause the timeout period expired.)]
                DNS server: 128.63.2.53 (h.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.112.36.4 (g.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.168.200.5 (CM-DC1-NY01)
                   All tests passed on this DNS server
                   Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
                DNS server: 192.168.200.6 (cm-dc-NY01.cmedia.local.)
                   All tests passed on this DNS server
                   Name resolution is functional._ldap._tcp SRV record for the forest root domain is registered
                   DNS delegation for the domain  _msdcs.cmedia.local. is operational on IP 192.168.200.6
                DNS server: 192.203.230.10 (e.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.228.79.201 (b.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.33.4.12 (c.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.36.148.17 (i.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.5.5.241 (f.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 192.58.128.30 (j.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 193.0.14.129 (k.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 198.41.0.4 (a.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 199.7.83.42 (l.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 199.7.91.13 (d.root-servers.net.)
                   All tests passed on this DNS server
                DNS server: 202.12.27.33 (m.root-servers.net.)
                   All tests passed on this DNS server
             Summary of DNS test results:
                                                Auth Basc Forw Del  Dyn  RReg Ext
                Domain: cmedia.local
                   cm-dc-NY01                  PASS PASS PASS PASS PASS WARN n/a
                   CM-DC1-NY01                 PASS PASS PASS PASS PASS WARN n/a
             ......................... cmedia.local passed test DNS
          Starting test: LocatorCheck
             GC Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             PDC Name: \\cm-dc-NY01.cmedia.local
             Locator Flags: 0xe00003fd
             Time Server Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             Preferred Time Server Name: \\cm-dc-NY01.cmedia.local
             Locator Flags: 0xe00003fd
             KDC Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             ......................... cmedia.local passed test LocatorCheck
          Starting test: FsmoCheck
             GC Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             PDC Name: \\cm-dc-NY01.cmedia.local
             Locator Flags: 0xe00003fd
             Time Server Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             Preferred Time Server Name: \\cm-dc-NY01.cmedia.local
             Locator Flags: 0xe00003fd
             KDC Name: \\CM-DC1-NY01.cmedia.local
             Locator Flags: 0xe00071fc
             ......................... cmedia.local passed test FsmoCheck
          Starting test: Intersite
             Skipping site Default-First-Site-Name, this site is outside the scope provided by the command line arguments
             provided.
             ......................... cmedia.local passed test Intersite

  • Rdp://full%20address=s: IP or DNS Name is not user friendly... Can rdp:// IP or DNS Name be assumed as the full address in Microsoft Remote Desktop?

    We would like to request Microsoft Remote Desktop (MRD) to behave the same as the open source CoRD.app on OS X with respect URL resolution.
    Example:MRD will resolve from Terminal rdp://full%20address=s:<IP or DNS Name>, but not rdp://<IP or DNS Name>
    As the OS will respect any of the following protocols in Terminal or browser:
    afp://<username>@<IP or DNS Name>
    cifs://<username>@<IP or DNS Name>
    ftp://<username>@<IP or DNS Name>
    ftps://<username>@<IP or DNS Name>
    http://<username>@<IP or DNS Name>
    https://<username>@<IP or DNS Name>
    smb://<username>@<IP or DNS Name>
    ssh://<username>@<IP or DNS Name>
    vnc://<username>@<IP or DNS Name>
    (<username> can be omitted to force authentication at connection)  it seems slightly redundant to force "full%20address=s:" in the URL.
    Can Version 8.0.1.6 be modified address this request?
    What is the proper way to report an enhancement request or bug?
    Thank you for your consideration.

    Hi,
    From your description it appears that you want to modify the pattern for assigning the rdp full address but this doesn’t support as per your requirement. That is the default string which we need to have for passing full address. 
    Hope it helps!
    Thanks.
    Dharmesh Solanki
    Please remember to mark the replies as answers if they help and unmark them if they provide no help. If you have feedback for TechNet Support, contact [email protected]

  • Error: Subject alternative name did not match site name (JavaME)

    When I try and connect to my RESTFul Web Service using SSL I get this exception:
    "Subject alternative name did not match site name".
    I did Google searches and as far as I can tell my 'Subject' matches my 'site name'. I know this because when I connect using my Browser (IE or Firefox) they say our SSL certificate is a-ok (no mismatches). Also, my Windows Mobile 5/6 REST application works fine under SSL. So, I am doubting it's a server side setting?
    Godaddy's root certificate is installed on the Java Emulator. If I disable the root cert I get a different error.
    I am using the QwertyDevice Emulator with 'identified_third_party' security. Wireless Toolkit 2.5.2 and NetBeans Mobility 6.0.1.
    My Web Server is IIS 6.0 that is hosting a WCF .NET 3.5 WebService using the webHttp binding (for those who don't know that's makes it a RESTFul Web Service).
    IIS 6.0 Settings:
    -Web Service is under Default Web Site and in Default Application Pool.
    -'Require secure channel (SSL)' is selected as well as 'Require 128-bit encryption'.
    Here is my client Code:
    InputStream is = null;
    HttpConnection conn = null;
    try
    conn = (HttpConnection)Connector.open("https://ourwebserver.ourdomain.com/RESTServer/Service.svc/REST/getmyopentasks/", Connector.READ_WRITE);
    conn.setRequestProperty("Authorization", "Basic " +
    BasicAuth.encode(userName, password));
    conn.setRequestMethod(HttpConnection.GET.toString());
    conn.setRequestProperty("Content-Type", "application/x-www-form-urlencoded");
    is = conn.openInputStream();
    catch (IOException ex)
    ex.printStackTrace();
    A few notes: We are using Basic HTTP Authentication, and "BasicAuth.encode" method is, a helper method, that I found code for out on the Internet. It works fine though.
    Because when I run this above code with SSL turned off, on the server, it works fine (authenticating and getting RESTFul XML back). I did try HttpsConnection as well. Did not work. Same SSL error.
    When this line is executed: "is = conn.openInputStream();" I get this exception: "Subject alternative name did not match site name". I have searched this forum and Google and can't figure this one out! Thanks!

    When I try and connect to my RESTFul Web Service using SSL I get this exception:
    "Subject alternative name did not match site name".
    I did Google searches and as far as I can tell my 'Subject' matches my 'site name'. I know this because when I connect using my Browser (IE or Firefox) they say our SSL certificate is a-ok (no mismatches). Also, my Windows Mobile 5/6 REST application works fine under SSL. So, I am doubting it's a server side setting?
    Godaddy's root certificate is installed on the Java Emulator. If I disable the root cert I get a different error.
    I am using the QwertyDevice Emulator with 'identified_third_party' security. Wireless Toolkit 2.5.2 and NetBeans Mobility 6.0.1.
    My Web Server is IIS 6.0 that is hosting a WCF .NET 3.5 WebService using the webHttp binding (for those who don't know that's makes it a RESTFul Web Service).
    IIS 6.0 Settings:
    -Web Service is under Default Web Site and in Default Application Pool.
    -'Require secure channel (SSL)' is selected as well as 'Require 128-bit encryption'.
    Here is my client Code:
    InputStream is = null;
    HttpConnection conn = null;
    try
    conn = (HttpConnection)Connector.open("https://ourwebserver.ourdomain.com/RESTServer/Service.svc/REST/getmyopentasks/", Connector.READ_WRITE);
    conn.setRequestProperty("Authorization", "Basic " +
    BasicAuth.encode(userName, password));
    conn.setRequestMethod(HttpConnection.GET.toString());
    conn.setRequestProperty("Content-Type", "application/x-www-form-urlencoded");
    is = conn.openInputStream();
    catch (IOException ex)
    ex.printStackTrace();
    A few notes: We are using Basic HTTP Authentication, and "BasicAuth.encode" method is, a helper method, that I found code for out on the Internet. It works fine though.
    Because when I run this above code with SSL turned off, on the server, it works fine (authenticating and getting RESTFul XML back). I did try HttpsConnection as well. Did not work. Same SSL error.
    When this line is executed: "is = conn.openInputStream();" I get this exception: "Subject alternative name did not match site name". I have searched this forum and Google and can't figure this one out! Thanks!

  • DNS Name is not resolved.

    We have VPN 3005 Concentrator (4.7.1) and VPN client 5.0.3. We setup Split tunneling.
    When some user opens the application, sometimes the DNS name is resolved, sometimes it is not.
    When the DNS name is NOT resolved, we manually put in the IP address of the server. Then, the application is open.
    How do we make DNS resolve consistently?
    Thanks.

    You check to check the split-dns settings. Also can this local DNS server (split tunnelled) resolve those names even without the VPN?
    Regards
    Farrukh

  • Posting date in AFRU and 2lis_04_p_arbpl data source is not matching

    Hi Experts,
    We are facing an issue with 2LIS_04_P_ARBPL data source, posting date in AFRU table and in data source is not matching.
    For example: we booked an activity confirmation of value 100 on 01.01.2015 posting date, Counter 1, Operation 10
    For the same operation another counter is confirmed on 01.02.2015 posting date.
    So, in AFRU table:
    Prod Order     Operation     Confirmation Number     Counter     PostingDate     Activity
    1001               10               8001                             1              01.01.2015       100
    1001               10               8001                             2              01.02.2015       0
    In 2lis_04_p_arbpl data source, counter field is missing due to which only 1 record is coming which is:
    Prod Order     Operation     Confirmation Number     Counter     PostingDate     Activity
    1001               10               8001                             1              01.02.2015       100
    In data source, activity of value 100 is coming on 01.02.2015 date instead in AFRU table it is booked on 01.01.2015 posting date by which we are unable to match the value in query which is based on posting date.
    Please help on this.
    Thanks,
    Sameer

    Hi Sameer,
    Please check on which date the production order has status as "completed".
    It could be on 01.02.2015.
    Thanks,
    Vimal

  • Lightroom v. 3.6 and Sony A99 RAW does not match

    I recently bought the newest Sony A99 camera, but it seems L.v. 3.6 does not manage this (aparently new) type of RAW-pictures.
    Do I have to buy the L.v.4 or can I use v. 3.6 with changing some settings?
    Thank you

    Hello mJim,
    It works. Thank you for your help.
    Eugene
    2013/3/30 jim01403 <[email protected]>
       Re: Lightroom v. 3.6 and Sony A99 RAW does not match  created by
    jim01403 <http://forums.adobe.com/people/jim01403> in *Photoshop Lightroom
    - View the full discussion<http://forums.adobe.com/message/5192043#5192043

  • The java and sql object type  was not matched

    My table(Oracle10.2) has a varying arrays column. For mapping to java classes, I use JDeveloper(10.1.3.1.0) to generate java classes. Then I try to insert a record into this varrying arrays column with java. While it always complaints java.sql.SQLException.the java and sql object type was not matched. I can not find the reason.
    My java code:
                   StructDescriptor structdesc = StructDescriptor.createDescriptor(
                             "VARRAY_SEQ", con);
                   int nid=20;
                   int pid=546;
                   BigDecimal mynid=new BigDecimal(nid);
                   mynid=mynid.setScale(0, BigDecimal.ROUND_HALF_UP);
                   BigDecimal mypid=new BigDecimal(pid);
                   mypid=mypid.setScale(0, BigDecimal.ROUND_HALF_UP);
                   Object[] attributes = { "ASDF", mynid, "Developer", mypid,
                             "rwretw" };
                   STRUCT Rel = new STRUCT(structdesc, con, attributes);
                   stmt.setObject(8, Rel);
                   stmt.execute();
                   stmt.close();
    And the STRUCT is
    public RelSeq(String nucl, java.math.BigDecimal neId, String nuor, java.math.BigDecimal pId, String phor) throws SQLException
    { _init_struct(true);
    setNucl(nucl);
    setNeId(neId);
    setNuor(nuor);
    setPId(pId);
    setPhor(phor);
    }

    My table(Oracle10.2) has a varying arrays column. For mapping to java classes, I use JDeveloper(10.1.3.1.0) to generate java classes. Then I try to insert a record into this varrying arrays column with java. While it always complaints java.sql.SQLException.the java and sql object type was not matched. I can not find the reason.
    My java code:
                   StructDescriptor structdesc = StructDescriptor.createDescriptor(
                             "VARRAY_SEQ", con);
                   int nid=20;
                   int pid=546;
                   BigDecimal mynid=new BigDecimal(nid);
                   mynid=mynid.setScale(0, BigDecimal.ROUND_HALF_UP);
                   BigDecimal mypid=new BigDecimal(pid);
                   mypid=mypid.setScale(0, BigDecimal.ROUND_HALF_UP);
                   Object[] attributes = { "ASDF", mynid, "Developer", mypid,
                             "rwretw" };
                   STRUCT Rel = new STRUCT(structdesc, con, attributes);
                   stmt.setObject(8, Rel);
                   stmt.execute();
                   stmt.close();
    And the STRUCT is
    public RelSeq(String nucl, java.math.BigDecimal neId, String nuor, java.math.BigDecimal pId, String phor) throws SQLException
    { _init_struct(true);
    setNucl(nucl);
    setNeId(neId);
    setNuor(nuor);
    setPId(pId);
    setPhor(phor);
    }

  • Entourage: "Event and computer time zones do not match."

    Since installing the latest update to the Mac OS (10.4.6) I have a glitch with Entourage (Office 2004 for Mac v. 11.2.3) and I believe it has something to do with the Mac OS. See below for explanation:
    When adding a new calendar event to the calendar, I get an error which reads:
    "Event and computer time zones do not match. In Calendar views, the event time is adjusted to display correctly." This is not true. I've checked the time zones in both my OS and Entourage and that is not the problem.
    It must have to do with how it interacts with the latest update of the Mac OS. I had not updated software on my laptop for a while, and it did not exhibit this error, so as a test, I downloaded and installed the latest version of Office and tested Entourage: no error message. To be sure, I restarted the computer and tried again: no error. Then I downloaded and installed all of the latest updates to the Mac OS using Software Update: I got the error. So, I think the problem is the interaction between the latest update of Office 2004 for Mac and the latest Mac OS or maybe even just something in the Mac OS.
    There are plenty of people complaining about this on the newsgroups at Mactopia. I'm not sure who needs to repair this problem - Apple or Microsoft, but does anyone know if there will be a patch issued by Microsoft to fix the problem? Or maybe my assessment is wrong and you have another solution?
    Thanks very much for your help with this problem.
    Dual G5 2.0 and Powerbook titanium   Mac OS X (10.4.6)  

    I am in Ohio (eastern time) and I am also having this problem. It is not annoying but my problem is I am not able to schedule any meeting on Entourage. (It will not show if the person I am inviting is busy or not). They use the Exchange server in my company, and I read on the microsoft site that public folders and hence the calendar items are not synced. But seems like this page is for Office X and not 2004. Any clues? Is the time error related to me not able to schedule meetings? I am using latest 10.4 and Entourage 2004.
    http://www.microsoft.com/mac/resources/resources.aspx?pid=resourcekits&rk=office x&article=/mac/officex/ork/KnownIssuesEntourage.xml
    MacBook Pro, iMac G4   Mac OS X (10.4.7)   2 GHz, 2G RAM

Maybe you are looking for