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.
Related
I am developing an app with a login system in flutter. Using postgresql I can access to an external database located in a raspberry. All works perfect until the network of the device changes. So here are my questions:
How can I access to a database from a device connected to a different network? Is that possible?
If not, how could it be the correct way to do it? or what should I read and/or learn to apply this funcionality?
Thank you.
This question is not Postgres specific.
You connect to servers over TCP/IP protocol using servers IP address or it's FQDN, fully qualified domain name. If your device is mobile and changes network, you can use some dynamic IP service or your own name servers.
Setting up a port forwarding system is also possible.
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.
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.
We have a domain, and there are some computers in this domain. we applied some many policies like password policy and etc to this domain which makes it easier for us to control the use PC in our organization. Now I wonder if it is possible to stipulate a certain configuration for every PC's firewall in our domain or to force every PC in domain at least block some certain Ports and maybe IPs. Can any one help me? Is it possible?
You can create GPOs for the firewall here:
Computer Configuration -> Administrative Templates -> Network -> Network Connections -> Windows Firewall
Then apply them to your computer group(s) as desired.
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.