Solved

Difference between windows and ios wireless

Posted on 2012-03-26
6
602 Views
Last Modified: 2012-04-03
On my ipod at work, I had problems staying connected to one of the internal wireless networks, so I put in a fixed ip and it worked great. The other wireless is dhcp on a completely separate network, and it also works great, and gets the proper IP address.  Is there a way to do this with Windows devices, where you can configure the wireless connections independently?  I thought on Windows if you put in a fixed ip for wireless it wouldn't work on any other wireless network because it wouldn't have the right IP.
0
Comment
Question by:maharlika
6 Comments
 
LVL 38

Expert Comment

by:hdhondt
ID: 37768907
Yes, you can give Windows a fixed IP address. Every IP connection (wired, wireless...) can, and should, have a separate address, all of which can be individually set to DHCP or fixed.

If you go to network setup, click on TCP/IP and then click the Properties button, you can change the settings there.

Especially for wireless, you really should leave it set to DHCP. Different networks may have completely different settings, so, if you fix the IP address for one network, it may not work on the next one, or may even give a duplicate address conflict which would affect others on the network, too.
0
 
LVL 79

Expert Comment

by:David Johnson, CD, MVP
ID: 37770918
Wireless is a per network (SSID) setting (static vs dynamic ip)
0
 
LVL 3

Author Comment

by:maharlika
ID: 37771514
I don't understand how this works on windows wireless. The only option I see for putting in a fixed IP address is on the wireless adapter settings, which will change it for all wireless connections.  this means if I put in a fixed IP in one location, it won't work on wireless in another network unless I change it back to dhcp on the adapter settings.  The ipod lets me change the dhcp/fixed ip settings per ssid, but windows does not
0
DevOps Toolchain Recommendations

Read this Gartner Research Note and discover how your IT organization can automate and optimize DevOps processes using a toolchain architecture.

 
LVL 45

Expert Comment

by:Craig Beck
ID: 37772160
You need to use 3rd party software to do this, such as NetSwitcher...

http://www.netswitcher.com/
0
 
LVL 44

Expert Comment

by:Darr247
ID: 37772172
> where you can configure the wireless connections independently?

I believe hdhondt inferred you meant "independently from the wired adapter" in which case their answer is accurate.

Microsoft's Wireless Zero Configuration service does not allow you to configure the DHCP/static IP settings separately between wireless networks, though some 3rd-party connection managers (such as those from Broadcom, Atheros or Intel) might allow that.
0
 
LVL 26

Accepted Solution

by:
akahan earned 500 total points
ID: 37790013
Windows allows you to solve this problem, more or less.

You don't say what version of Windows you're using.  I'm going to assume XP.  Windows 7 is similar, but not EXACTLY the same.

In XP:

Start/Control Panel/Network Connections.  Right-click on the wireless network connection.  Choose Properties.
Under the General tab, choose TCP/IP.
Click the Properties button.
Under General, check "obtain an IP address automatically," and "Obtain DNS server address automatically."

Next, choose the Alternate Configuration tab (next to the General tab).
Under Alternate Configuration, enter the static IP address information that works for your troublesome wireless network: Ip address, Subnet mask, default gateway, and DNS servers.  Hit OK and exit all the way out.

Now here's what will happen:

When you attempt to connect to a wireless network, the machine will FIRST try the "General" settings:  It will try to get a connection using DHCP.  If it does, great.  If it is unable to do so, it will next try the static settings you've entered under "Alternate Configuration."  This will connect you to the network you're having trouble with, the one that only connects using a static IP address.

So nearly all the time, you'll successfully get a DHCP address; on your one crappy network, it will first attempt DHCP and fail; and will then try static.  So there will be a somewhat longer delay before it connects successfully (because it's trying and failing at DHCP first), but it'll connect after a bit.
0

Featured Post

Is Your AD Toolbox Looking More Like a Toybox?

Managing Active Directory can get complicated.  Often, the native tools for managing AD are just not up to the task.  The largest Active Directory installations in the world have relied on one tool to manage their day-to-day administration tasks: Hyena. Start your trial today.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

Suggested Solutions

Title # Comments Views Activity
Question to Pivot table 1 53
BXR1220 speakers- does not work on another PC 12 102
perfect consistent volume 6 46
Problem to App source 6 39
Whether you believe the “gig economy,” as it has been dubbed, is the next big economic paradigm shift (https://www.theguardian.com/commentisfree/2015/jul/26/will-we-get-by-gig-economy) or an overstated trend (http://www.wsj.com/articles/proof-of-a-g…
Digital marketing agencies have encountered both the opportunities and difficulties that emerge from working with a wide-ranging organizations.
The Bounty Board allows you to request an article or video on any technical topic, or fulfill a bounty request to earn points. Watch this video to learn how to use the Bounty Board to get the content you want, earn points, and browse submitted bount…
Saved searches can save you time by quickly referencing commonly searched terms on any topic. Whether you are looking for questions you can answer or hoping to learn about a specific issue, a saved search can help you get the most out of your time o…

770 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question