- LOGMEIN HAMACHI TUNNEL PROBLEM WINDOWS 7 UPDATE
- LOGMEIN HAMACHI TUNNEL PROBLEM WINDOWS 7 REGISTRATION
- LOGMEIN HAMACHI TUNNEL PROBLEM WINDOWS 7 PC
- LOGMEIN HAMACHI TUNNEL PROBLEM WINDOWS 7 PROFESSIONAL
DLL: C:\Users\Sean\AppData\Local\Temp\MSI28BE.tmp, Entrypoint: SearchVersions MSI (c) (18:B8) : Invoking remote custom action. MSI (c) (18:94) : Note: 1: 2235 2: 3: ExtendedType 4: SELECT `Action`,`Type`,`Source`,`Target`, NULL, `ExtendedType` FROM `CustomAction` WHERE `Action` = 'SearchVersions' To avoid posting an exceptionally long log file, I've include only the relevant section of the log file:Īction 16:43:30: SearchVersions. Which produced an error log that pointed to the file causing the intallation to fail. Runing the MSI from the desktop, using your suggested command symantics:Ĭ:\Users\Sean\Desktop> msiexec.exe /i hamachi.msi /l*v "C:\Users\Sean\Desktop\hamachiinstall.log" You might have to use a different machine as a tunnel endpoint, if not.That was helpful - your tip led me to a solution. If so, I don't know if Hamachi supports referring to the DC via the non-Hamachi interface. It sounds like you have the Hamachi interface on the DC itself. (that refers to 2000, but it should work for 2003, too)
LOGMEIN HAMACHI TUNNEL PROBLEM WINDOWS 7 REGISTRATION
Instead, I think you want to disable DNS registration on the virtual Hamachi adapter. Multihoming a domain controller can cause issues.
You probably don't want to add an entry for the second IP. Records are referred to as Locator DNS resource records.īecause the remote site can't contact the DC via its internal IP, remote users can't "find" that server to log on.
Resource records provide the client with the names and IP addresses of To find domain controllers in a domain or forest, a client queries DNSįor the SRV and A DNS resource records of the domain controller. Both types of records are necessary for theįunctionality of the domain controller locator (Locator) mechanism. The service (SRV) and address (A) resource records are dynamically During the installation of Active Directory,
LOGMEIN HAMACHI TUNNEL PROBLEM WINDOWS 7 UPDATE
Type and the dynamic update protocol, as described in the RFC 2136.Īctive Directory uses DNS as the location mechanism for domainĬontrollers, enabling computers on the network to obtain IP addresses Is required to support the service (SRV) resource record In order for a DNS server to be able to support Active Directory, the server Network shares on the server are working perfectly- it seems this issue only affects the ability to log on as domain users.Īny ideas what is going on and how I can fix this?Īs you suspected, it's DNS at the remote site. The (automatically-assigned) DNS for the XP system is the gateway router's IP: 192.168.1.1 There are no problems accessing shares on the server over the VPN link.
Ping server's Hamachi VPN IP address = SUCCESS
Ping 192.168.1.50 = FAIL (pinging DC by its private IP) Ping = FAIL (however pinging the server's FQDN is successful when done to PCs at the main office) Here are the results of pinging various combinations of hostnames and IP addresses for the domain controller from the XP system:
LOGMEIN HAMACHI TUNNEL PROBLEM WINDOWS 7 PC
I've tried removing the PC from the domain and re-joining in case it was simple broken trust relationship problem (and even tried a different PC) but the issue is always the same. The other symptom is that domain users do not show up properly on the Local Users and Groups MMC snap-in (it shows only their SIDs, without the corresponding domain user names). This does not happen when the PC is taken to the main office and connected to the LAN, and subsequent attempts to log on remotely succeed after this is done (but only due to cached credentials- the underlying problem remains and new users will still not be able to log on at the remote site). The issue is that domain users at the remote site see the following message when they try to log on: The XP desktop was joined to the domain across the VPN connection without any problems.
LOGMEIN HAMACHI TUNNEL PROBLEM WINDOWS 7 PROFESSIONAL
We have a Windows XP Professional desktop at a remote site connected to our SBS 2003 domain controller at the main office via VPN (LogMeIn Hamachi).
0 kommentar(er)
