We've been having a few problems recently with a wireless connection and our firewall.

When our VP comes into the office, his laptop picks up the wireless address 192.168.1.3. I'm happy that he can pick up a wireless connection and get an IP address..... but 192.168.1.3 is the address of the firewall of the company.

Our DHCP scope is set at 192.168.1.140 - 192.168.1.240

The only way I can think of why this happens is when he as at home he gets the 192.168.1.3 address from his wireless router, then he brings it in here, the DHCP server sees his laptop as the Gateway, and no Internet traffic goes in and out because of it. I asked him if he shuts down his computer when he brings it back and forth and he said that he does.

How is this happening that the wireless connection still keeps that address moving inbetween domains? Is there a solution to this problem?

The only ones I can think of are:
A. Reconfiguring his wireless router at home to 192.168.2.x
B. Giving him a static IP
C. Beating my head off of my desk

I've talked to 2 consulting companies, and Cisco themselves and no one can figure out why this is happening or how to keep it from happening.

Sure I have come up with 2 very simple solutions, but it shouldn't be like this in the first place. My wireless network at home is 192.168.1.x. I have no problems with my laptop, or my iPhone with their addresses and coming into the office.

he does not have a static IP, that was the first thing I checked. I looked over all of the WAP's and none of them are doing DHCP. only our DHCP server gives out addresses.

it's not everyday that this happens with his laptop. but it has been happening about once a week lately. the last time this happened (yesterday morning) it was keeping all of the settings from his home.

it's just not flushing out all of the settings when he disconnects/shutsdown.

Go to the command prompt, type ipconfig /release and then, once it's released and shows all 0's, type ipconfig /renew.

At the computer store that I work at computers that connect wirelessly often pick up a "wrong" ip address just because of the way the network is set up. Apparently whoever set it up, did so incorrectly, and sometimes computers that connect wirelessly will pick up an IP from the wrong DHCP server, or something like that.

Might or might not work, but it only takes a few seconds to try.

Edit: and I seriously doubt this is the case, and it might not even make a difference, but his home network and the network at the office don't have the same name do they?

he doesn't "need" his wireless in the office since he docks his laptop on his desk connected with ethernet cable.

the /release /renew does work, but it doesn't solve the problem. his computer still carries his wireless ip address 10 miles from his house to the office.

edit: I just realized after typing this that he does not use Windows built in program to connect to a wireless network, he uses Intel or something. Maybe he has that setup to get that address. he doesn't have a static IP address either. I'll have to play with his computer tomorrow and figure out some stuff.

Ok, so the problem is not that you can't get it to work, the problem is just that you can't get it to work completely automatically? Well, you could always switch it over from using that utility to using Windows and then simply configure Windows to work correctly. I know nothing abuot that utility though. You could try playing with it.