I have a laptop that was recently factory restored and given to another user in our office. Previously, it connected to the local network fine, and was able to ping our local office server (which is our AD server, and our local DNS server (windows 2012 R2)), via IP address and domain (CENTURION). After factory restore, the laptop can no longer ping via domain, nor can join the local AD domain, because it says the domain can't be found.
Could somebody please offer me some assistance in fixing this?
I have tried both wirelessly and wired, and have also issued the following commands:
netsh int ip reset
ipconfig /flushdns
I have even set DHCP to automatic, and manually set the IP, and the primary dns server is set to my local dns server's IP address.
So I was able to fix this. Newer versions of Windows do not allow single-label domain names (like EXAMPLE). Our local domain is 'CENTURION'.
There was a regedit flag I had to enable in order to allow connecting to this.
From what I read online, this applies to Anything above Windows 7.
[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\Netlogon\Parameters] and add a new DWORD: AllowSingleLabelDnsDomain with a value of 1.
Upon restarting, you can connect to single label domains.
Related
I have tried to connect a page which is hosted in ec2 instance. It is showing server timed out error but rest of my collegues able to connect to it.
I use mac laptop
Things i did:
clearing cache
tried to change my network
3.tried in incognito mode
nothing works. Thanks in advance
Things to normally check:
Confirm that the EC2 instance is running a web server (try to access it from somewhere else, or login to the instance and try curl localhost)
Confirm that the EC2 instance is in a public subnet (defined as the subnet having a Route Table entry that points to an Internet Gateway)
Confirm that the Security Group associated with the EC2 instance is permitting inbound access on port 80 (for HTTP) and possibly port 443 (for HTTPS)
Confirm that you are attempting to access the instance via a public IP address (not a private IP address) and that the public IP address is currently associated with the instance
Don't change default NACL rules
You mention "rest of my colleagues able to connect" but you don't mention from where they are accessing the instance. Quite clearly, something is either different with your computer or with the network that you are using. I would suggest you focus on:
The Security Group "inbound" rules, to confirm that they are not blocking access
Try to connect from a different network (eg home vs office vs tethered via your phone) to confirm that your network is not blocking access
If you are connecting from the same network as your colleagues, then the problem is on your computer. This is unlikely because the timeout normally indicates a lack of network connectivity (rather than software configuration).
I'm setting up an Active Directory in Windows 2012 for user authentication in Windows 10. Server and client PCs are not in the same area, therefore, it is a Wan connection.
For testing purposes, all firewalls are off. Server's public IP is 34.207.231.151 and a has a local IP 172.31.13.53. DNS in the server is active and correctly points the desired domain adir.school1.com to local IP. Client PCs use the server's public IP as DNS, that works well because if I ping adir.school1.com, I get the servers local IP.
If I try to join the clients to the domain it says Cannot contact with an Active Directory Domain Controller in the domain. In the details it says that the DNS was successfully query and it identified a domain controller but it cannot contact the Domain Controller.Which is expected as it cannot connect to 172.31.13.53 outsdie the LAN. How do I configure my ADDS to be reachable outside the LAN?
It looks like about your network configurations. I draw a basic network configuration.
Also you can see a wan network here. Gateway is very important at this point.
In order to use ADDS through WAN, you do need a VPN. I could not use this solution, though, because the admins of the network did not want to open the required ports for VPN overt the firewall.
The solution was to change the network configuration of the entire campus so our virtual server became part of the internal nerwork (which is a bunch of LANs with gateways) and voila!, the ADDS was reachable from all other computers. Still, not accesible outside the campus, but inside it works perfectly.
How could to connect to Azure DB from any ip that uses Azure,
Without setting the range 0.0.0.0 - 255.255.255.255 in the firewall?
If by connect to Azure DB from any ip that uses Azure you mean any applications running in Azure, then it is possible to do so. In the portal where you configure firewall rules, simply turn on "Allow access to Azure services".
What this does is that it creates a special firewall rule with Start/End IP address as 0.0.0.0. You will not see this firewall rule in portal though.
To do this thing programmatically, simply create a new firewall rule and set the Start/End IP address as 0.0.0.0.
However if your question is about any client IP address that connects to your database, then I would agree with #Aravind's comment above. You should not allow direct connection to your databases from anywhere but only facilitate it via a proxy service/API layer as mentioned by him.
I have a veru bizare issue.
When trying to connect via RDP to a remote laptop which has been taken off the network for a few days. When connected again to the network, i cannot RDP into it using DNS name but can using IP. OS is windoes 7 Enterprise x64 using AD.
Taking it off the domain and adding it again does not help.
Any suggestions?
Can you ping the DNS name via the command prompt? Sounds like rejoining the network may have assigned a different IP to the alias.
To rule out firewall issues you could also disable firewalls on both temporarily and try again - though I doubt a firewall is the problem because you're able to access it via the IP address.
DNS was the issue. It was not releasing the associated IP. Had to purge all old data and schedule auto periodic purge.
So I have a network setup with a Windows Server 2003 machine running as the Domain Controller. All of the domain users are physically connected over Ethernet except for one which due to it's location requires being connected over our Wifi (which until now hasn't had any domain users). The PC is running Windows XP SP3 and was successfully able to join the domain, but it cannot see any other computers in the domain. Also, when looking in the Active Directory on the server, it also does not show the computer.
I tried unjoining and rejoining the domain but it didn't resolve the issue. I also tried connected the computer over a different AP but again it didn't resolve the issue. After researching online I was only able to come up with information regarding how routers will sometimes interfere with the server's DHCP settings which can cause this issue, but I don't believe this would be relevant as the devices are setup as access points and not routers.
Any ideas?
Not an answer, but a troubleshooting idea. Run 'ipconfig /all' from commandline on this machine and a LAN connected machine and compare. Specifically compare DNS settings, and the IP addresses to make sure they are in the same range.