Wireless LAN "problem"/questions

This is more of an annoying situation than a problem, but I really would like to find an answer if there is one.

I have a wired/wireless LAN supported by a D-Link DI-514 (802.11b) router with a cable internet connection. My desktop computer is connected to the router via Ethernet, as is a docking station serving either of two laptops. The laptops also connect to the LAN via wireless if off the dock. All three computers have ZoneAlarm installed.

The desktop always uses the same assigned IP, as do the laptops (different IP for each computer) if connected via Ethernet, so connection between computers is immediate.

When connecting via wireless, however, the laptop's assigned IPs change from time to time, from NNN.NNN.N.111 to NNN.NNN.N.112 or NNN.NNN.N.113, and so on, with the last three digits always increasing. I still have immediate access to the internet, but the only way the computers can connect to each other is if I edit the ZoneAlarm firewall settings in each computer to reflect the new IP assignment. This isn't usually a "problem ", but it is an annoying nuisance, as I'm not always near the desktop when booting one of the laptops.

In an effort to avoid having to edit ZA's settings all the time, I've tried assigning static IPs to the laptops in TCP/IP Properties, but they don't stick ... they revert to a dynamic IP setting as soon as the Properties sheet is closed.

So, two questions:

Why don't the newly assigned static IPs stick?

Is there a way to prevent this from happening, so that I don't have to keep editing the ZA firewall settings?​

Any input will be appreciated.

 

Just so I understand correctly are you modifying the TCP/IP propeties of the wireless NIC or the Wired NIC that are not sticking?
There are seperate properties for each.

Plus I think it would be a good idea of assighning an IP out of the DHCP scope.
Example would be: XXX.XXX.X.90

 

Hi Scott,

Thanks for the quick reply, as I'd like to get this resolved today, if possible.

I thought I was clear about my attempt to assign static IPs for the laptops, but I guess I wasn't. I was trying to assign them to the wireless NIC cards; the IPs for the Ethernet NICs don't change.

The laptops are recent model IBMs, and use their proprietary Access Connections software to manage connections. I was able to successfully assign static IPs, but had to create separate profiles (Ethernet and wireless) in each laptop in order to do so.

Unfortunately, where, before, the computers automatically switched to the faster Ethernet connection when placed on the dock, now I have to select the proper profile which, at least, is easier than editing ZA all the time when switching to wireless. Apparently, automatic switching isn't available when using static IPs..

 

My preference if the Laptop has XP SP2 is to let windows manage the wireless NIC and uninstall the IBM utility but thats just my opinion.

In the Windows Wireless Properties there should be a check box "Allow Windows to manage my Wireless properties ".
Thats not the exact contex because I dont have one in front of me to look at.

 

Problem is sometimes my reading comprehension isn't clear.

 

Both laptops have XP Pro SP2. I'll try your suggestion when I have more play time, but I'm inclined to leave things alone for now ... the IBM software is really quite easy to configure and use.

 

Scott ...

I uninstalled the IBM Access Connections software in one of the laptops, and established static IPs (below the DHCP range) with Windows for both the Ethernet and the wireless connections. I did the same with the Ethernet connection on the desktop, though I don't know if I needed to, as its dynamic IP always seemed to stay the same.

So, I now have a full-time wireless connection, even when the laptop is using the Ethernet connection (which seems a bit weird), and I no longer have to edit settings in ZoneAlarm. Switching between connections when moving the laptop onto or off of its dock is automatic ... no more having to select a profile.

I'm baffled by something else, though. With the desktop computer, router, and cable modem turned off, the laptop still "sees" my LAN and connects to it, which makes no sense to me. When so connected the laptop can't connect to the internet, which I do understand.

In the past, however, I've been able to connect to networks in other locations (airports, Starbuck's, my son's LAN in another city) and have internet access. To test this capability with the current setup, I connected to a neighbor's LAN (with his permission), but was unable to get online, which I don't understand.

I look to you, Newt, and TonyT as the experts in this field, so I'm hoping that one of you can provide an answer.

Addendum (edited)...

After a little more trial-and-error, I reinstalled the IBM Access Connections software and discovered that, although I have to create a profile for the wireless NIC, none is required for the Ethernet NIC. So, the statement in post #3 about selecting the proper profile no longer applies. I still have the Windows network connection settings in place, but Access Connections has an interface with which I'm familiar, and it's easy to use.

Further experimenting has led me to the conclusion that any network I connect to must have current internet access for me to be able to get online. I had assumed (incorrectly, I guess ) that any LAN would have internet access at all times, as mine normally does.

 

Whew!!!

So, are you good to go at this point?

 

A little long-winded, was I? Sorry 'bout that, but I was trying to provide as much detail as possible. Yeah, I seem to be good to go ... everything is working smoothly, even though I don't understand all of what's going on.