-1

I have established a server in the office using Windows Server 2008 R2 and Active Directory. And then created several users in Active Directory Users and Computers.

The PC users can successfully join the domain and log in using their username/passwords.

However, the laptop users with wireless connectivity are not able to join the domain and access the network. I checked laptops with ethernet cable, and they successfully logged in to domain. But when unplugging the ethernet cable and enabling the wireless, they cannot log in to domain any more.

How can I enable domain access for wireless clients?

If the problem is with DNS or DHCP, then, why does a laptop connect to domain with Ethernet cable, but not with wireless connection (with the same exact DNS configurations) !!!? The only difference is being connected wired or wireless !! Am I wrong !!?


Edit 1

We are using a D-Link 2750U ADSL Modem which has 4 ethernet ports and wireless enabled. We use this modem both for accessing the internet, and also for establishing the server-client network. The server PC is connected via ethernet cable and has Windows Server 2008 R2 running, while the clients are some PC and some laptop, mostly Windows 7.

Edit 2

I tried the ping example.local command in laptops. When connected with ethernet cable, it has nice and successful reply; but when connected via wireless (WLAN), the ping does not respond, and gives the following error: "Ping request could not find host example.local. Please check the name and try again."

Edit 3

It seems that I have to enable something in the server or active directory, so that wireless clients can find, connect, and access the server.

Edit 4

This is what I've done to the DNS settings of clients (both wired PCs and wireless laptops): In the properties section of IPv4 (in client computers), I choose the Use the following DNS server addresses, and in front of Preferred DNS server, I type the IPv4 of the server PC. This works perfect for wired PCs, but not for wireless laptops.

Edit 5

Unfortunately, we do not have static IP. So we are using dynamic IP (for both server and clients). Is it possible to configure DNS and DHCP with dynamic IP?

Edit 6

The following pictures show the Network Connection Details for both the Server and the wireless Client:

Server

enter image description here

Client

enter image description here

Edit 7

I tried ping 192.168.1.34 with wireless laptop. The result was request time out, followed by trying to connect to 192.168.1.33 (!!), which again resulted in request time out.

It was really strange. So I tried ping 192.168.1.35 from wireless laptop. It replied successfully, but with 192.168.1.33 IP !!!!

The 192.168.1.33 IP belongs to another win-7 PC in the office, which used to host the shared drives and shared printers when we used win-7 homegroup (instead of server) in the past.

Edit 8

I checked the IP of the computers again. They have changed. The Server PC is now 192.168.1.35 and the wireless laptop is 192.168.1.33

Edit 9

I'm not able to ping the wireless laptop. Right now, the laptop's IP is 192.168.1.36, and when I do ping 192.168.1.36 from server PC, it says Destination Host Unreachable !! However, the wireless laptop is able to connect to internet with wifi.

Edit 10

I tried 192.168.1.1 in a web browser with the wireless laptop, and it worked successfully. The browser opened the D-Link Modem page.

  • 1
    Please update the question with details of your network architecture with respect to the server, wired network and wireless network. Can wireless users ping the domain controller? – Phil May 5 '16 at 11:38
  • Thanks @Phil for your comment. What information do you exactly want? I'm relatively new to server things. How can I ping the domain controller? – Omid1989 May 5 '16 at 11:43
  • Dear @William, I found your post here (serverfault.com/questions/601614/…) that you had solved the problem. Would you please describe the solution? – Omid1989 May 5 '16 at 11:48
  • If you log on to the laptop using a local account, connect to the wireless, and then ping the Windows domain name (e.g., example.com or example.local), what happens? – Todd Wilcox May 5 '16 at 12:49
  • You're not getting the correct DNS servers on the laptop when it is connected wirelessly. How is DHCP being handled? I suggest using the server to provide DHCP and hand out the same information to both wired and wireless clients. – Todd Wilcox May 5 '16 at 13:04
0

I solved this problem with the following method:

  1. Type 192.168.1.1 to enter modem settings.
  2. Type username and password.
  3. Go to Setup
  4. Go to Wireless
  5. Go to Wireless Basic
  6. Un-check the Enable MultiAP Isolation option.
  7. Apply.

Your Answer

By clicking “Post Your Answer”, you agree to our terms of service, privacy policy and cookie policy

Not the answer you're looking for? Browse other questions tagged or ask your own question.