• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 360
  • Last Modified:

Cannot browse internet via WiFi, but can via ethernet cable

Users cannot browse the internet when connected to WiFi, but they can when connected to the LAN via cable.

DHCP and DNS is done on the server (SBS 2011). 192.168.1.3

Modem/Router is Netcomm NB604N. 192.168.1.1

When a client connects to WiFi, the connection shows Limited Connectivity.

If I set the IP details to static on a WiFi client and point the DNS to 192.168.1.3, the internet starts working.
0
cgruber
Asked:
cgruber
  • 4
  • 2
  • 2
  • +3
1 Solution
 
epichero22Commented:
If you're browsing with static IP settings, but not dynamic, then it's definitely a DHCP configuration error.  Is your wireless router giving them settings instead of the server?  Be sure that you only have one device managing DHCP.
0
 
Wylie BayesNetwork Technician IIICommented:
So when connected on wireless are the clients actually getting an IP via DHCP? Or is it getting set to a 169.xx.xx.xx address?

Is the wireless setup as Bridge?   If it is not setup as a bridge (AP MODE) then the NAT (Network Address Translation) will kill your DHCP traffic.  

If you wish you leave it as is, you need to have the wifi router also act as a DHCP server and hand out addresses on that subnet.  So all wireless clients would use the gateway address of the Wifi router, and all wired clients would use the gateway address of the Netcomm.

I would recommend changing the wireless router to a bridge (AP mode) and only run 1 DHCP server.
0
 
cgruberAuthor Commented:
DHCP is turned off on the modem/router.

When connected to wireless, clients get an IP address and the correct default gateway, but the DNS server comes up as 127.0.0.1
0
SMB Security Just Got a Layer Stronger

WatchGuard acquires Percipient Networks to extend protection to the DNS layer, further increasing the value of Total Security Suite.  Learn more about what this means for you and how you can improve your security with WatchGuard today!

 
cgruberAuthor Commented:
This page allows you to configure wireless bridge features of the wireless LAN interface. You can select Wireless Bridge (also known as Wireless Distribution System) to disable access point functionality. Selecting Access Point enables access point functionality. Wireless bridge functionality will still be available and wireless stations will be able to associate to the AP. Select Disabled in Bridge Restrict which disables wireless bridge restriction. Any  wireless bridge will be granted access. Selecting Enabled  enables wireless bridge restriction. Only those bridges selected in Remote Bridges will be granted access.
Click "Refresh" to update the remote bridges. Wait for few seconds to update.
Click "Apply/Save" to configure the wireless bridge options.

ap settings
0
 
cgruberAuthor Commented:
see above for current ap settings
0
 
Thomas GrassiSystems AdministratorCommented:
Go to the wireless network connection properties for the wifi  adapter

Select Internet protocol version 4 TCP/IPv4

On general tab

Obtain DNS Server address automatically. Must be selected

What do you have for that?

Ipconfig /all post
0
 
cgruberAuthor Commented:
These are iPhones, iPads, Galaxy phones, but anyway thats what you get

IP Address: 192.168.1.X
Subnet: 255.255.255.0
Gateway: 192.168.1.1
DNS: 127.0.0.1
0
 
Thomas GrassiSystems AdministratorCommented:
Maybe your wifi router is blocking port 53
Or the servers firewall

I would check the firewall settings
0
 
AkinsdNetwork AdministratorCommented:
DNS 127.0.0.1
Is that the address issued to the cliens. If yes, then that's the problem. Replace with actual address of the router
0
 
Wylie BayesNetwork Technician IIICommented:
If everything is set to "obtain automatically" then the DHCP server is delivering 127.0.0.1 as the DNS settings.

What do your wired clients get?

What are your other options on the ap settings page besides AP ?
0
 
profgeekCommented:
Are the devices showing 192.168.1.3 as their DHCP server?
0
 
AkinsdNetwork AdministratorCommented:
Check the DHCP scope and replace the 127.0.0.1 with 192.168.1.3
Force the clients to renew their IP
Everything should work afterwards
0

Featured Post

Receive 1:1 tech help

Solve your biggest tech problems alongside global tech experts with 1:1 help.

  • 4
  • 2
  • 2
  • +3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now