Firefox on Linux doesnt connect to .local domains

Hello,
im running FF 3.6.18 on Ubuntu (64bit, 32bit) and im not able to connect to any domain ending in .local (for example: apple.fruits.local). Name resolution is working, prefetching and fixup is disabled. Using FF on windows works without a problem with the same domain name - only in Linux it fails.

Hi!
Thats quite simpel:
.local domains belong to the zeroconf system ( linux: avahi, apple: bonjour, windows: zeroconf) - so if you enter a www.dummy.local than the request is not forwarded to the DNS server it is forwarded to the MDNS and in many networks simply not resolvable.
Turn of the avahi, bonjour or zeroconf service or daemon and it will work again
regards
Martin

Similar Messages

DNS: Client can't connect because .local domain isn't in DNS. How can I connect over the WAN to server.domain.local?

So my 2012 server is set up on the LAN with a .local domain name.
Remote Desktop Services are set up and remoteapp stuff works fine on the LAN.
I've set up port forwarding so I can connect to the server over the WAN too, but remoteapp stuff is a bit different. I can connect to the server by specifying the correct IP address. Giving a Web browser the address
https://serverIPAddress/RDWeb
lets me get the login screen and see the range of apps for me to run. I select one, the connectoid is downloaded correctly (in Chrome) and I click on the downloaded connectoid.
Unfortunately, rather than pursuing the sensible IP-address approach that I started with, the connectoid has been given the server's name on the LAN: server.domain.local. Clearly, the client machine tries to look this up but DNS hasn't heard of
it because it's a .local address.
I cannot be the only one to have come across this apparent oversight on Microsoft's part. Any ideas as to how this can sensibly be overcome? Obviously, I could put the IP address translation into every client's hosts file (and I've done this and shown it
works) but I've got too many clients to mess about like this. Anybody know 'the Microsoft way' to fix this?
Thank you for checking this out -- I am confident the details of the problem are completely specified in this query but, if I'm wrong, please ask.
Many thanks again,
Biffo

Hi,
I would like to suggest you to follow the checklist.
Checklist: Make RemoteApp Programs Available from the Internet
http://technet.microsoft.com/en-us/library/cc772415.aspx
Thanks.
Jeremy Wu
TechNet Community Support

DNS is incredibly slow on Lion 10.7.4 when connected to a .local domain

Im running Lion 10.7.4 and am connected to a .local domain. I've googled the problem and cant really work out if there is a fix or not.
I am also running VMWare Fusion on the same machine with Windows 7. neither Lion or Windows 7 are joined to the domain. The windows 7 VM browses the internet perfectly but lion is painfully slow.
My IP's are DHCP assigned and the search domain is xxxx.local
The VM is using bridged not NAT which is why the VM is perfming perfectly.
I know its something to do with the .local but cant change the TLD here so need a fix.
PLEASE HELPPPP

Im using Chrome and it happens in Safari and Firefox too. To be honest its not specifically web browsing. DNS is just ridiculously slow when connected to a .local domain.

I have 2 lan connections, 1 connect to local network server and other to internet, how do i configure firefox to open website on my local network connection and internet also

''locking as a duplicate - https://support.mozilla.com/en-US/questions/812283''
I have 2 local area connections in my computer, one connects to local office network server and another to the internet. when i use firefox i want to configure it to use it to connect to my local office network server website which has address as http://199.123.9.1 and also internet web address simultaneously,

I found the solution, myself, you need to go to network settings and then select manual proxy setting and provide the ip address of the internet server . that's all
"it is not OS setting up problem, around DNS and routing Problems." as stated by you,
anyway thanks.

Connect LDAP service to local domain

Is there anyone who can tell me if it's possible to connect form the LDAP service to a local domain?
I have made a new local domain with some groups and users in the Domain management in LC ES admin module.
Now I want to retrieve those users to my prcess in workbench with the LDAP service, but I can't get it to connect to the new domain (it works fine when I connect to our company AD).
I have tried with Base DN: DC=NewDomain,DC=local and Search filter: cn=* but with no luck :-(
Is it possible to connect to the local domaim from the LDAP service if it is, what should the "Base DN" look like and what are the atributes to use in the search filter?
Thanks
Søren

I think you are getting a few things mixed up.
When you create the users in a local domain, you're in fact creating them in the LiveCycle database. Not in a LDAP system. LiveCycle NEVER writes to an LDAP system. It only reads from it.
When LC integrates with an LDAP system (like when you create an enterprise domain in adminui), it connects to an external LDAP system and sychronizes with it. I also adds a copy of the users in its database.
The LDAP service does the same thing is the sense that it just connects to a external LDAP system to get a list of users.
If you want to query the users from the livecycle database you can use the User Lookup service (under Foundation) instead.
Jasmin

The processing of Group Policy failed because of lack of network connectivity to a domain controller

We are setting up a new AD environment with one AD/DC running DNS services, and a secondary DNS server configured with secondary zone. The problem is that none of the machines in the the domain are getting GPO.
When I run a gpupdate /force from a machine, I get the following output:
"Updating Policy...
User Policy update has completed successfully.
Computer policy could not be updated successfully. The following errors were enc
ountered:
The processing of Group Policy failed because of lack of network connectivity to
a domain controller. This may be a transient condition. A success message would
be generated once the machine gets connected to the domain controller and Group
Policy has succesfully processed. If you do not see a success message for sever
al hours, then contact your administrator.
To diagnose the failure, review the event log or run GPRESULT /H GPReport.html f
rom the command line to access information about Group Policy results."
While the system event log outputs the following:
"The processing of Group Policy failed because of lack of network connectivity to a domain controller. This may be a transient condition. A success message would be generated once the machine gets connected to the domain controller and Group Policy
has succesfully processed. If you do not see a success message for several hours, then contact your administrator."
All the machines that were joined to the domain are able to resolve in forward and reverse lookups, ping the DC and ping each other so I dont understand how the error can be resolved.
Here are few things I have tried:
1. I came across this KB which checked ok for me: http://support.microsoft.com/kb/241515
2. Made a copy of the default GPO, applied to a OU with one machine, and made sure to remove any GPO links from above
3. Enabled the following two local Group policies on a test member:
GP slow link detection
Startup policy processing wait time
4. Modified firewall to allow everything on both member and DC
5. Verified DSN logs, SRV records, access to sysvol ( added authenticated users to sysvol)
I have yet to figure out the reason for this issue. Has anyone seen anything like this before?

1. I checked the NIC, it only has one IP. and I followed your article. I set the primary DNS to its own IP and the secondary DNS to the loopback ip
2. This is a new DC and DNS server. I dont have old records yet. I also check the DNS event logs. No errors
3. I made sure the member server is pointing only to the only DC/DNS server
4. Here is the output from the dcdiag.... everything passed except, the Netlogons part. I'm not sure what means or how to fix it yet:
Starting test: NetLogons
* Warning BUILTIN\Administrators did not have the "Access this
computer
"* from network" right.
[hostname] An net use or LsaPolicy operation failed with error
1, Incorrect function..
......................... hostname failed test NetLogons
Complete output:
> hostname
Server: hostname.domain.local
Address: X.X.X.95
> ^C
C:\Windows\system32>
C:\Windows\system32>nslookup
> set type=all
>
>
>
> _ldap._tcp.dc._msdcs.domainname
_ldap._tcp.dc._msdcs.domain.local SRV service location:
priority = 0
weight = 100
port = 389
svr hostname = hostname.domain.local
hostname.domain.local internet address = X.X.X.95
> ^C
C:\Windows\system32>cd ..
C:\Windows>cd SYSVOL
C:\Windows\SYSVOL>cd sysvol
C:\Windows\SYSVOL\sysvol>dir
Volume in drive C has no label.
Volume Serial Number is F624-CDB2
Directory of C:\Windows\SYSVOL\sysvol
10/29/2014 08:25 PM <DIR> .
10/29/2014 08:25 PM <DIR> ..
10/29/2014 08:25 PM <JUNCTION> domain.local [C:\Windows\SYSVOL\domain]
0 File(s) 0 bytes
3 Dir(s) 63,971,037,184 bytes free
C:\Windows\SYSVOL\sysvol>dcdiag
Directory Server Diagnosis
Performing initial setup:
Trying to find home server...
Home Server = hostname
* Identified AD Forest.
Done gathering initial info.
Doing initial required tests
Testing server: Default-First-Site-Name\hostname
Starting test: Connectivity
......................... hostname passed test Connectivity
Doing primary tests
Testing server: Default-First-Site-Name\hostname
Starting test: Advertising
......................... hostname passed test Advertising
Starting test: FrsEvent
......................... hostname passed test FrsEvent
Starting test: DFSREvent
......................... hostname passed test DFSREvent
Starting test: SysVolCheck
......................... hostname passed test SysVolCheck
Starting test: KccEvent
......................... hostname passed test KccEvent
Starting test: KnowsOfRoleHolders
......................... hostname passed test
KnowsOfRoleHolders
Starting test: MachineAccount
......................... hostname passed test MachineAccount
Starting test: NCSecDesc
......................... hostname passed test NCSecDesc
Starting test: NetLogons
* Warning BUILTIN\Administrators did not have the "Access this
computer
"* from network" right.
[hostname] An net use or LsaPolicy operation failed with error
1, Incorrect function..
......................... hostname failed test NetLogons
Starting test: ObjectsReplicated
......................... hostname passed test
ObjectsReplicated
Starting test: Replications
......................... hostname passed test Replications
Starting test: RidManager
......................... hostname passed test RidManager
Starting test: Services
......................... hostname passed test Services
Starting test: SystemLog
A warning event occurred. EventID: 0x000003F6
Time Generated: 03/04/2015 18:23:06
Event String:
Name resolution for the name ctldl.windowsupdate.com timed out after
none of the configured DNS servers responded.
......................... hostname passed test SystemLog
Starting test: VerifyReferences
......................... hostname passed test VerifyReferences
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 : emcdsm
Starting test: CheckSDRefDom
......................... emcdsm passed test CheckSDRefDom
Starting test: CrossRefValidation
......................... emcdsm passed test CrossRefValidation
Running enterprise tests on : domain.local
Starting test: LocatorCheck
......................... domain.local passed test LocatorCheck
Starting test: Intersite
......................... domain.local passed test Intersite
C:\Windows\SYSVOL\sysvol>

The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller. If the license compliant check cannot be completed, the server will automatically shut down in 0

i need a help. I am new in company and have to solve this problem.
My colleague did a migration from Small Business server 2003 to Foundation 2008, about 1 year ago. After few days, he got this error message in title. Server turn off about once a month. He worked following:
joined new server Foundation to the Domain
dcpromo on new Server
migration (he said that he worked step-by-step with tutorial)
demote on old Server SBS 2003
disconnect old server from domain. This old is not in function now.
New server have just 3 computer accounts. The Forest functional level is Server 2003.
I've did dcdiag:
C:\Users\Administrator>slmgr.vbs /dli
C:\Users\Administrator>dcdiag
Directory Server Diagnosis
Performing initial setup:
   Trying to find home server...
   Home Server = server2008
   * Identified AD Forest.
   Done gathering initial info.
Doing initial required tests
   Testing server: Default-First-Site-Name\SERVER2008
      Starting test: Connectivity
         ......................... SERVER2008 passed test Connectivity
Doing primary tests
   Testing server: Default-First-Site-Name\SERVER2008
      Starting test: Advertising
         ......................... SERVER2008 passed test Advertising
      Starting test: FrsEvent
         ......................... SERVER2008 passed test FrsEvent
      Starting test: DFSREvent
         ......................... SERVER2008 passed test DFSREvent
      Starting test: SysVolCheck
         ......................... SERVER2008 passed test SysVolCheck
      Starting test: KccEvent
         ......................... SERVER2008 passed test KccEvent
      Starting test: KnowsOfRoleHolders
         ......................... SERVER2008 passed test KnowsOfRoleHolders
      Starting test: MachineAccount
         ......................... SERVER2008 passed test MachineAccount
      Starting test: NCSecDesc
         ......................... SERVER2008 passed test NCSecDesc
      Starting test: NetLogons
         ......................... SERVER2008 passed test NetLogons
      Starting test: ObjectsReplicated
         ......................... SERVER2008 passed test ObjectsReplicated
      Starting test: Replications
         ......................... SERVER2008 passed test Replications
      Starting test: RidManager
         ......................... SERVER2008 passed test RidManager
      Starting test: Services
         ......................... SERVER2008 passed test Services
      Starting test: SystemLog
         A warning event occurred. EventID: 0x8000001D
            Time Generated: 03/08/2012   09:59:45
            Event String:
            The Key Distribution Center (KDC) cannot find a suitable certificate
to use for smart card logons, or the KDC certificate could not be verified. Sma
rt card logon may not function correctly if this problem is not resolved. To cor
rect this problem, either verify the existing KDC certificate using certutil.exe
or enroll for a new KDC certificate.
         An error event occurred. EventID: 0xC0001B61
            Time Generated: 03/08/2012   10:09:56
            Event String:
            A timeout was reached (30000 milliseconds) while waiting for the Liv
eUpdate service to connect.
         An error event occurred. EventID: 0xC0001B58
            Time Generated: 03/08/2012   10:09:56
            Event String:
            The LiveUpdate service failed to start due to the following error:
         ......................... SERVER2008 failed test SystemLog
      Starting test: VerifyReferences
         ......................... SERVER2008 passed test VerifyReferences
   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 : BREG
      Starting test: CheckSDRefDom
         ......................... BREG passed test CheckSDRefDom
      Starting test: CrossRefValidation
         ......................... BREG passed test CrossRefValidation
   Running enterprise tests on : BREG.local
      Starting test: LocatorCheck
         ......................... BREG.local passed test LocatorCheck
      Starting test: Intersite
         ......................... BREG.local passed test Intersite
C:\Users\Administrator>
I did nslookup:
C:\Users\Administrator>nslookup
Default Server: UnKnown
Address: ::1
and this:
C:\Users\Administrator>ntdsutil
ntdsutil: roles
fsmo maintenance: connections
server connections: connect to server server2008
Binding to server2008 ...
Connected to server2008 using credentials of locally logged on user.
server connections: q
fsmo maintenance: select operation target
select operation target: list roles for connected server
Server "server2008" knows about 5 roles
Schema - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site-Name,CN
=Sites,CN=Configuration,DC=BREG,DC=local
Naming Master - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site-
Name,CN=Sites,CN=Configuration,DC=BREG,DC=local
PDC - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site-Name,CN=Si
tes,CN=Configuration,DC=BREG,DC=local
RID - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site-Name,CN=Si
tes,CN=Configuration,DC=BREG,DC=local
Infrastructure - CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site
-Name,CN=Sites,CN=Configuration,DC=BREG,DC=local
select operation target:
Did also slmgr.vbs /dli and got:
name:Windows Server(R) ServerWinFoundation edition
Description: Windows operating System - Windows Server(R),
OEM_COA_NSLP channel
Partial product key:.......
License Status:Licensed
thanks for help, in advance

I forgot to say that it is the only DC in the domain.
and this is DNS test
Directory Server Diagnosis
Performing initial setup:
   Trying to find home server...
   * Verifying that the local machine server2008, is a Directory Server.
   Home Server = server2008
   * Connecting to directory service on server server2008.
   * Identified AD Forest.
   Collecting AD specific global data
   * Collecting site info.
   Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=BREG,DC=local,LDAP_SCOPE_SUBTREE,(objectCategory=ntDSSiteSettings),.......
   The previous call succeeded
   Iterating through the sites
   Looking at base site object: CN=NTDS Site Settings,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BREG,DC=local
   Getting ISTG and options for the site
   * Identifying all servers.
   Calling ldap_search_init_page(hld,CN=Sites,CN=Configuration,DC=BREG,DC=local,LDAP_SCOPE_SUBTREE,(objectClass=ntDSDsa),.......
   The previous call succeeded....
   The previous call succeeded
   Iterating through the list of servers
   Getting information for the server CN=NTDS Settings,CN=SERVER2008,CN=Servers,CN=Default-First-Site-Name,CN=Sites,CN=Configuration,DC=BREG,DC=local
   objectGuid obtained
   InvocationID obtained
   dnsHostname obtained
   site info obtained
   All the info for the server collected
   * Identifying all NC cross-refs.
   * Found 1 DC(s). Testing 1 of them.
   Done gathering initial info.
Doing initial required tests
   Testing server: Default-First-Site-Name\SERVER2008
      Starting test: Connectivity
         * Active Directory LDAP Services Check
         Determining IP4 connectivity
         * Active Directory RPC Services Check
         ......................... SERVER2008 passed test Connectivity
Doing primary tests
   Testing server: Default-First-Site-Name\SERVER2008
      Test omitted by user request: Advertising
      Test omitted by user request: CheckSecurityError
      Test omitted by user request: CutoffServers
      Test omitted by user request: FrsEvent
      Test omitted by user request: DFSREvent
      Test omitted by user request: SysVolCheck
      Test omitted by user request: KccEvent
      Test omitted by user request: KnowsOfRoleHolders
      Test omitted by user request: MachineAccount
      Test omitted by user request: NCSecDesc
      Test omitted by user request: NetLogons
      Test omitted by user request: ObjectsReplicated
      Test omitted by user request: OutboundSecureChannels
      Test omitted by user request: Replications
      Test omitted by user request: RidManager
      Test omitted by user request: Services
      Test omitted by user request: SystemLog
      Test omitted by user request: Topology
      Test omitted by user request: VerifyEnterpriseReferences
      Test omitted by user request: VerifyReferences
      Test omitted by user request: VerifyReplicas
      Starting test: DNS
         DNS Tests are running and not hung. Please wait a few minutes...
         See DNS test in enterprise tests section for results
         ......................... SERVER2008 passed test DNS
   Running partition tests on : ForestDnsZones
      Test omitted by user request: CheckSDRefDom
      Test omitted by user request: CrossRefValidation
   Running partition tests on : DomainDnsZones
      Test omitted by user request: CheckSDRefDom
      Test omitted by user request: CrossRefValidation
   Running partition tests on : Schema
      Test omitted by user request: CheckSDRefDom
      Test omitted by user request: CrossRefValidation
   Running partition tests on : Configuration
      Test omitted by user request: CheckSDRefDom
      Test omitted by user request: CrossRefValidation
   Running partition tests on : BREG
      Test omitted by user request: CheckSDRefDom
      Test omitted by user request: CrossRefValidation
   Running enterprise tests on : BREG.local
      Starting test: DNS
         Test results for domain controllers:
            DC: server2008.BREG.local
            Domain: BREG.local
               TEST: Authentication (Auth)
                  Authentication test: Successfully completed
               TEST: Basic (Basc)
                  The OS
                  Microsoft Windows Server 2008 R2 Foundation (Service Pack level: 1.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
                  [00000007] Intel(R) 82566DM-2 Gigabit Network Connection:
                     MAC address is 00:19:99:86:E9:62
                     IP Address is static
                     IP address: 192.168.1.250
                     DNS servers:
                        192.168.1.250 (server2008.breg.local.) [Valid]
                        127.0.0.1 (server2008.breg.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: 192.228.79.201 [Valid]
                     Name: c.root-servers.net. IP: 192.33.4.12 [Valid]
                     Name: d.root-servers.net. IP: 128.8.10.90 [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: 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: BREG.local.
                     Delegated domain name: _msdcs.BREG.local.
                        DNS server: server2008.breg.local. IP:192.168.1.250 [Valid]
               TEST: Dynamic update (Dyn)
                  Warning: Failed to add the test record dcdiag-test-record in zone BREG.local
                  [Error details: 9017 (Type: Win32 - Description: DNS bad key.)]
                  Test record dcdiag-test-record deleted successfully in zone BREG.local
               TEST: Records registration (RReg)
                  Network Adapter
                  [00000007] Intel(R) 82566DM-2 Gigabit Network Connection:
                     Matching CNAME record found at DNS server 192.168.1.250:
                     cb30439d-35e0-4add-ae6c-e7f281295520._msdcs.BREG.local
                     Matching A record found at DNS server 192.168.1.250:
                     server2008.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.221dc40b-9d51-48cf-a3a3-e3daf251197f.domains._msdcs.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _kerberos._tcp.dc._msdcs.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.dc._msdcs.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _kerberos._tcp.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _kerberos._udp.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _kpasswd._tcp.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.Default-First-Site-Name._sites.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _kerberos._tcp.Default-First-Site-Name._sites.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.gc._msdcs.BREG.local
                     Matching A record found at DNS server 192.168.1.250:
                     gc._msdcs.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _gc._tcp.Default-First-Site-Name._sites.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.pdc._msdcs.BREG.local
                     Matching CNAME record found at DNS server 192.168.1.250:
                     cb30439d-35e0-4add-ae6c-e7f281295520._msdcs.BREG.local
                     Matching A record found at DNS server 192.168.1.250:
                     server2008.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.221dc40b-9d51-48cf-a3a3-e3daf251197f.domains._msdcs.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _kerberos._tcp.dc._msdcs.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.dc._msdcs.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _kerberos._tcp.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _kerberos._udp.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _kpasswd._tcp.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.Default-First-Site-Name._sites.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _kerberos._tcp.Default-First-Site-Name._sites.dc._msdcs.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.Default-First-Site-Name._sites.dc._msdcs.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _kerberos._tcp.Default-First-Site-Name._sites.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.gc._msdcs.BREG.local
                     Matching A record found at DNS server 192.168.1.250:
                     gc._msdcs.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _gc._tcp.Default-First-Site-Name._sites.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.Default-First-Site-Name._sites.gc._msdcs.BREG.local
                     Matching SRV record found at DNS server 192.168.1.250:
                     _ldap._tcp.pdc._msdcs.BREG.local
         Summary of test results for DNS servers used by the above domain
         controllers:
            DNS server: 2001:500:1::803f:235 (h.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:1::803f:235
[Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
            DNS server: 2001:500:2d::d (d.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:2d::d
[Error 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:503:ba3e::2:30 (a.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:503:ba3e::2:30
[Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
            DNS server: 2001:503:c27::2:30 (j.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:503:c27::2:30
[Error details: 1460 (Type: Win32 - Description: This operation returned because the timeout period expired.)]
            DNS server: 2001:7fd::1 (k.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:7fd::1
[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 because 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 because the timeout period expired.)]
            DNS server: 128.63.2.53 (h.root-servers.net.)
               All tests passed on this DNS server
            DNS server: 128.8.10.90 (d.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.1.250 (server2008.breg.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.BREG.local. is operational on IP 192.168.1.250
            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: 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: BREG.local
               server2008                   PASS PASS PASS PASS WARN PASS n/a
         ......................... BREG.local passed test DNS
      Test omitted by user request: LocatorCheck
      Test omitted by user request: Intersite

Windows Server 2012 Foundation, in a Workgroup - "The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller"...

Every few days we see two dialogs with the following messages:
Dialog 1, title: Check for Licensing Compliance is Incomplete
The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller.
Dialog 2, title: Check for Licensing Compliance is Incomplete
The server did not finish checking the license compliance. If the server is joined to a domain, make sure that the server can connect to a domain controller. If the license compliance check cannot be completed, the server will automatically shut
down in 8 day(s) 23 hour(s) 0 minute(s).
The server is not (and never has been) joined to a domain or had any DC roles installed. In fact its still connected to the default Workgroup.
The server was configured in our office and never showed this message until it was installed on site. The main difference from what I can see is that when installed on site it was given a static IP address and does not have any DNS settings in the network
adapter properties.
I have scoured a number of forums on this error but in almost every other instance of this error message the servers are connected to a Domain Controller and the solutions generally are linked to dis-joining and rejoining the domain. Unfortunately this is
not an option for this scenario.
I initially thought that adding some relevant DNS server IP address may resolve the issue, however, we have the exact same model server configured exactly the same running at a different site that does not experience this problem. This server also has no
DNS server configured.
I have seen a post that suggests turning off the servers "Foundation Checking", but I'm unsure how to do this.

Thanks for your response Vivian.
I can confirm that this server is not (and never has been) a member of any active directory, it is configured as a Workgroup server. It was initially configured on a network that does have an active directory, but was never joined to it. During that time it
never displayed these messages.
The server was moved into production on a different site and network and setup with a static IP address.The site network does have its own active directory but the server was not joined to it. It is whilst on this new network that these messages began.
Since my original post DNS servers have been added and the Microsoft activation has been verified, however, the messages are still appearing.
There are only 2 user accounts configured on this server. The local admin account and another local admin user.
The remote desktop services roles have been installed but not yet configured. I don't think that has any bearing on this scenario though.
The description of this error in the above "Introduction to Windows Server 2012 Foundation" link states:
This error occurs when the server cannot finish checking the requirements for the root domain, forest trust configuration, or both. It usually happens when the server cannot connect to a domain controller. If the situation persists, the server will
shut down 10 days after the first time the compliance check failed. Each time this error message occurs, it will state the actual time remaining before the server will shut down. If you restart the server after it has shut down because of non-compliance, the
server will shut itself down again in 3 days.
The above description leads me to the following question - In a Workgroup environment, does the server still try to contact a domain controller to establish a level of trust? If this is the case could it be that the server can no longer see the initial DC
on its new network and this is what is triggering the messages?
Am I clutching at straws here?

Can't connect to local web server

I'm not quite sure when this happened; I think it was upgrading to iPhoneOS 3.x but I can't swear to that (currently running 3.1). Anyway, the problem is that, whether from my app or even simply using Safari, I can't connect to a local webserver. If I'm on one computer in my office (working over WiFi just like my iPhone), and type "http://192.168.1.110/file", where 110 is a different computer, Safari will display the page just fine. But if I'm using my iPhone in the office, on the same network, and type the same URL, it will not connect. For SURE this used to work, and I haven't changed any settings on my network or on my iPhone for that matter.
No problem with connecting to external websites, clearly.

Web services are not relevant to DNS host names. You'll need to configure a default domain name for whatever is being used as the local domain, whether that is established via System Preferences or via DHCP settings. If your Windows box is running a DNS server, you'll need to set the Mac DNS resolver address at the Windows DNS server.

Why do I get error "The LDAP server is unavailable" while connecting to external domain via sync connection in SharePoint UPSA ?

Hello,
I am trying to connect to external domain via UPS Account having "Replicate Directory changes" permission on external domain while creating sync connection in UPSA.
I have checked below URLS :
http://social.technet.microsoft.com/Forums/en-US/1912bf88-8fec-4b5d-9d1e-a42db8318e33/ldap-server-is-unavailable-sharepoint-2010-user-synchronization?forum=sharepointadminprevious
http://social.technet.microsoft.com/Forums/en-US/6525d3aa-9197-42a2-aea0-190b84ac8356/the-ldap-server-is-unavailable?forum=sharepointadminprevious
And looks like its network connectivity issue - and hence I have verified that port 389 is open by infra team.
Note : I am able to connect to local AD , does it make sense that port is not open for external domain ?
Can anyone please let me know what can be the issue ?
Your help will be highly appreciated as I am struggling to fix this issue since quite long time but no luck yet.
Thank you in advance.
Kind regards,
Dipti Chhatrapati

Hi Dipti,
If you have Two-Way trust relationship then not sure if you have tried below:
Create a folder on the SharePoint server
Go to Folder properties - Security tab
Try adding user of the external domain on the folder
Please let us know if you are able to add the user or not. If you are able to add then it means that the connection and trust is proper and you should be able to create sync connection in UPA without any issues or else there is some issue with the connectivity
or the trust which is configured.
Please also make sure that you have given permissions to sync account as per below TechNet:
http://technet.microsoft.com/en-us/library/hh296982(v=office.15).aspx
Replicate Directory changes permissions are also required on cn=configuration container, below are the steps:
Grant Replicate Directory Changes permission on the cn=configuration container
Use this procedure to grant Replicate Directory Changes permission on the cn=configuration container to an account.
To grant Replicate Directory Changes permission on the cn=configuration container
On the domain controller, click Start, click Run, type adsiedit.msc, and then click OK.
If the Configuration node is not already present, do the following:
In the navigation pane, click ADSI Edit.
On the Action menu, click Connect to.
In the Connection Point area of the Connection Settings dialog box, click Select
a well know Naming Context, select Configuration from the drop-down list, and then click OK.
Expand the Configuration node, right-click the CN=Configuration... node, and then click Properties.
In the Properties dialog box, click the Security tab.
In the Group or user names section, click Add.
Type the name of the synchronization account, and then click OK.
In the Group or user names section, select the synchronization account.
In the Permissions section, select the Allow check box next to the Replicating
Directory Changes (Replicate Directory Changes on Windows Server 2003) permission, and then click OK.
Kind regards,
Bhavik K Jain
Please ensure that you mark a question as Answered once you receive a satisfactory response.

Migrate existing users from local domains to Open Directory.

Here is the environment I'm working with:
Small local environment (8-10) users. Everyone is on their own laptop, everyone is authenticating to their local directories. Network files are stored on a server, with everyone using a single shared user ID to authenticate and access the files.
I have just installed a Xserve, and it is now serving DNS, DHCP, NTP, WWW. I want to setup Open Directory in Master mode, create user IDs for everyone, and then assign permissions to the shared files area.
The one part that I'm not sure how to approach is the local laptops. If user "John Doe" has a local ID "jdoe" that he has been using on his local laptop, how does he migrate over to being "jdoe" in the OD domain, while reatining his "local" home directory and files? The problem I think I'll have is that when I create "jdoe" on the domain, he will have a UID of (say) 10001, but his local UID is 501 (as is the UID of all the other employees since they are all the first user on each of their respective laptops.) so when he logs back into his laptop after it has been attached to the OD domain, I assume that the laptop will see "jdoe" from the OD domain as a new user and create a new home for him (with the UID:10001), so now John cannot see any of his old files and such.
Also, as a side question: I've worked with Windows ID before, and I know once you join a windows computer to a domain and then login to it, it creates a new user and caches the authentication info, so that when the laptop is not connected to the corporate network, the user can still login and work. Does Open Directory do the same on the laptops?
Thanks for any help.

Retaining password is a manual process of asking the user what his or her password is and then creating it in OD.
As for migration of account, it is rather simple, provided the short name of the user remains consistent across directory systems. For example, if you have a user named Joe User and his short name is juser with a home folder in /Users/juser. And you create the same account in OD. You can do these few short actions.
1: Bind system to the domain
2: From the Admin account, and using Terminal from root, navigate to /var/db/dslocal/nodes/Default/users and find the plist file for the user (in our example, juser.plist).
3: Delete the file using rm
4: Restart the machine or restart Open Directory
5: Log in as the admin user and change ownership of the users home folder. Recall that when the user is in the local domain, the UID was likely 502, 503, etc (you do have a standard local admin at 501 right?) Now that the user is in OD, the UID will be 4 digits, something like 1027. So understanding that user attributes and user data are independent, you now have a folder in /Users titled juser and owned by uid 50x. You need to make it owned by juser from the OD domain. User this:
sudo chown -R juser /Users/juser
6: Log out of the admin account
7: Log in as the user after choosing Other at login window.
Assuming you have your OD account set up properly, you will likely be asked to confirm the caching of the users credentials. This will path you right back into the user's home folder and all will be right with the world.
This is simple and quick. If the shortnames are different, throw an mv into the mix to rename the home folder to match the domain shortname. If you have no local admin, then you will need to reset DSLocal and start again.

RDS - .local domain and external users. Best way to get rid of SSL warnings

I am evaluating MS RDS as a possible solution for a VDI implementation at the college I work for. When we setup our AD years ago we set it up as a .local domain. I am running into issues with the .local machine name on the connection broker for
external users. I know for internal domain systems we can setup the self signed .local cert as a trusted root cert to bypass the self signed untrusted warning but for the bulk of our users which will be using systems external to our domain they
will get the SSL warning about the self signed certificate when they try to connect to a remote app or a desktop.
Initially I thought if I setup a local AD CA that we could setup a trust relationship with the SSL cert. After further reading I believe that this would only work for systems internal to our domain and we would still have the issue with external devices.
The other option would be to tell our users to click the box to never display the warning message again and to go on or to add the self signed cert to their trusted list. Of course when ever you ask the user to do something there will be issues. We
have also found that in our testing that we can not seem to connect via the web portal with a macbook. We get an error that there is a problem with the trust relationship with the server after we login and click on an app or a desktop to connect. We
have been able to connect with iOS devices.
We could of course rename the .local domain to a .edu domain which would permit us to use our wildcard certificate but that is a major undertaking that we don't want to cross at the moment. I think I might have some up with a solution and wanted to
bounce the idea off of those on this forum.
If we setup a second domain on campus that is not a .local. Join the non internet facing RDS systems to this new domain that would have a SSL cert that was trusted and then setup a full trust relationship between the two domains such that users and
systems in one domain could communicate with the systems in the other domain would that remove the certificate warnings for external users?

Hi AKlein,
Initially I thought if I setup a local AD CA that we could setup a trust relationship with the SSL cert. After further reading I believe that this would only work for systems internal to our domain and we would
still have the issue with external devices.
Just add the root CA certificate of the internal CA into Trusted Root Certification Authorities store on external clients manually (or through group policy if there is an external domain), then SSL certificate warning would be gone.
We could of course rename the .local domain to a .edu domain which would permit us to use our wildcard certificate but that is a major undertaking that we don't want to cross at the moment.
Yes, renaming domain is not recommended due to its complexity.
If we setup a second domain on campus that is not a .local. Join the non internet facing RDS systems to this new domain that would have a SSL cert that was trusted and then setup a full trust relationship between
the two domains such that users and systems in one domain could communicate with the systems in the other domain would that remove the certificate warnings for external users?
If you are setting up a new domain with two way trust, then root CA certificate of the internal CA still needs to be distributed manually (or through group policy). If you are setting up a child domain, then enterprise CA would be trusted within the same
forest.
As long as there are enough external users and devices to manage, an external private network exists and extra domain management tasks are acceptable, then setting up a new domain is a good choice since domain provides secure boundary.
Or, you could just create a new site from the other network location, which saves you from creating a new domain, new users and trust.
Best Regards,
Amy
Please remember to mark the replies as answers if they help and un-mark them if they provide no help. If you have feedback for TechNet Subscriber Support, contact
[email protected]

Outlook 2013 cannot connect to local Exchange 2013 server

Server name EXCHANGE: is Domain controller for (domainname.local), DNS server and Exchange 2013
Has UCC CA cert successfully installed for (exchange.domainname.com)
External Outlook connections, Web Outlook and autodiscover work fine.
local DNS points autodiscover.domain.com & exchange.domainname.com to internal IP
I have used the above configuration many time for Exch2010/Outlook 2010 and it works great.
PROBLEM: Outlook 2013 clients on a local domain member autoconfigure (through autodiscover) but report a certificate error that the names do not match. When I force the acceptance for the cert error the outlook13 account setups with an exchange server
of "BIG LONG GUID"@domainname.com which cannot resolve and outlook fails.
Please help..

Hi ,
I have recently installed the exchnage 2013 as follow
one CAS and Two mail box DAG
so I was facing similier issue outlook clients were not able not see the CAS
so here are the magic solution :
1-created SRV recored for autodiscover same as acbrown2010 done
above in his reply
2-created
A record for autodiscover and the IP same as CAS IP
3-created
an internal Certificate in CAS server "create a new certificate request " and
include all names such CAS , MB's , Autodiscover this step to avoid the warning message during outlook setup because self sign certificates in ex2013 not helping
after that I have tested the outlook and was working fine NO GUID and NO certificates warning

EM error: Fatal NI connect error 12537, connecting to: (LOCAL=NO)

When I start EM DB Console with "emctl start dbconsole" then following error occures every 10 seconds:
Fatal NI connect error 12537, connecting to:
(LOCAL=NO)
VERSION INFORMATION:
TNS for Linux: Version 11.2.0.1.0 - Production
Oracle Bequeath NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
TCP/IP NT Protocol Adapter for Linux: Version 11.2.0.1.0 - Production
Time: 13-JUN-2012 15:41:53
Tracing not turned on.
Tns error struct:
ns main err code: 12537
TNS-12537: TNS:connection closed
ns secondary err code: 12560
nt main err code: 0
nt secondary err code: 0
nt OS err code: 0
opiodr aborting process unknown ospid (24598) as a result of ORA-609
Wed Jun 13 15:42:03 2012Regards, Azer Imamaliyev

note: ORA-609 TNS-12537 and TNS-12547 in 11g Alert.log [ID 1116960.1] gives you a number of causes and possible solutions.
Eric

Adding alternative FQDN for local domain.

Hi,
I'm trying to configure RDS for my standalone Windows Server 2012 Essentials and it's almost done.
(Probablly) last thing i need to do is to change FQDN for my local domain to .com to use RDS externaly.
So, like i said, i've done dyndns config, added ssl cert, configured RDWeb, RD Gateway, RD License and RD Broker.
Now, when i'm logging into remote.mydomain.com/RDWeb , i can login with Active Directory credentials, get rdp i try login into server. But i can only try, becuase there is an error about wrong FQDN for server (know and not new error for anyone). So, what I
had done was changing FQDN for my domain by this powershell script http://gallery.technet.microsoft.com/Change-published-FQDN-for-2a029b80 (if anyone had problems with digitally unsigned script, google for "Set-ExecutionPolicy Unrestricted"), in
theory, this script changed FQDN, but in reality, i still have same problem trying to connect externally.
I also read that i should add new DNS Zone for my .com domain and there add (A) record for my subdomain for remote desktop, that points to internal IP adress of my server. When i tried that, it was even worse because i couldn't even open RDWeb site. When that
dns zone was deleted, everything came back to previous state.
And now i'm here, out of ideas. Any suggestion what I did wrong? Maybe it was something with this DNS Zone for .com ? Maybe there should be Zone, but not normal one but "stub zone"?
I would be happy for any suggestion.

" suspect we may have a basic mis-understanding of what each of us is trying to say. Let me try again.
There are (at least) three ways to reach a LAN computer from the internet with Essentials. Remote Web Access, direct RDP and VPN. There are also third party solutions, such as Go To My PC and Log Me In. The third party type
usually involve a subscription model with recurring charges, the others may involve a fee for SSL certificates, but they are (usually) much less expensive and do not rely on a third party."
Yes, i can agree we difinitelly had problem with mis-uderstanding so, sorry for that. I was talking about direct RDP to my server because Anywhere Access is already configured (but remote desktop from there to server opened only Essential Dashboard, that's
why i left this solution). Also, like i said, i'm aware of risks and i'll
take responsibility for that.
"Direct RDP is configured at the router and points the port (3389, but it can be changed) to the IP of the device you want to contact. then, simply opening the RDP applet on your remote computer and typing in the public IP of the router/firewall
will automatically connect you to the chosen computer. This is a very high security risk and should be avoided when ever possible."
Here is double facapalm for me - when you wrote about 3389 TCP port, i got enlightenment that i didn't do that (because i ealier tried to work on 443 with Anywhere Access and forgot about it), also information i got after tries to connect weren't usefull neither
- because Windows gave me back information about wrong FQDN, i was strictly focused on that problem, but like we know now, problem was in much different place. When i opened that port, everything started to be like i wanted (i also find out, after testing
RDP client from remoteapp in web menu that why i'm using this when i want to used direct RDP anyway). So much facepalm.
Next thing for now will be different port then 3389 and in future, VPN instead of direct RDP.
Anyway, really, thanks for help!

Firefox on Linux doesnt connect to .local domains

Similar Messages

Maybe you are looking for