SQL Connection fails on Wi-Fi switch on but works with LAN enabled

_{Friday, June 1, 2012 12:54 PM}

When I plugin my laptop to my corporate network, till the point of time my hardware Wi-Fi switch is on, my computer is not able to communicate to SQL Server. It says server not found but the moment I turn off the switch, using LAN I am able to find the SQL Server on the network. 

Any reasons?

_{Friday, June 1, 2012 1:17 PM ✅Answered | 1 vote}

can you ping the SQL Server whilst connected via wi-fi?  If so, try telnet-ing to the port SQL Server's listening on

Thanks,

Andrew Bainbridge
SQL Server DBA

Please click "Propose As Answer" if a post solves your problem, or "Vote As Helpful" if a post has been useful to you

_{Monday, June 4, 2012 3:25 PM ✅Answered}

Here are some detailed troubleshooting steps. How to Troubleshoot Connecting to the SQL Server Database Engine

I would especially attempt to connect using the IP Address and port number. It sounds like the WI-FI connection and the LAN connection are on different subnets. That's why you get an IP address in a different range. Connecting by to SQL Server name, can require using the SQL Server Browser service, which uses UDP (user datagram protocol), and UDP is often not passed through routers.

Rick Byham, Microsoft, SQL Server Books Online, Implies no warranty

_{Friday, June 1, 2012 1:06 PM}

are there any firewalls on the wireless router?  If so, you'll need to open up the appropriate ports.  Can you ping the SQL Server whilst connected via wi-fi?

Thanks,

Andrew Bainbridge
SQL Server DBA

Please click "Propose As Answer" if a post solves your problem, or "Vote As Helpful" if a post has been useful to you

_{Friday, June 1, 2012 1:13 PM}

Both Wi-Fi and LAN are same corporate network.

_{Monday, June 4, 2012 1:14 PM}

Ping (ICMP) seems to be be working fine in both Wi-Fi on and off cases. However there is a small difference between the ping outputs.

In Wi-Fi mode, I am getting an external IP address response (as a name resolution for the server) whereas in LAN mode, an internal IP address is shown.  And interestingly the IP address shown seems to be owned by 

as indicated by Ip2Location webservice.

Does this behavior has some thing to troubleshoot our issue?