Before this board dies a slow and painful death, perhaps it could finally provide one positive impact on society and help me with this problem.

I've got AT&T Uverse with the 2WIRE wireless network router it uses and it sucks. It constantly craps out and needs a reboot. We've had support out a half-dozen times, etc...anyway, I thought it might be better to connect a Cisco wireless access point to broadcast the network and bypass the 2WIRE altogether.

I've connected the Cisco to the 2WIRE via an ethernet port. The Cisco, preconfigured, immediately begins broadcasting an unsecured wireless network. I think "great, I'm almost there". But, when I try to access the Cisco administrative settings using the default 192.168.1.245, it does not connect. My 2WIRE uses a different IP for the default gateway. My IP Structure is 192.168.1.XXX. I'm guessing it is some kind of IP conflict but I don't know how to get around it. I've connected the CISCO directly to a computer, no luck. Also given my computers a static IP and tried it with no luck either.

Any ideas on how I can get to this administrative page so I can setup the network security?

_________________
You know me like that.

Racist.

_________________

I'm half Mexican-half Italian, so I can get away with it.

_________________
You know me like that.

Can you turn off the wireless on the 2WIRE?

_________________
You do not talk to me like that! I work too hard to deal with this stuff! I work too hard! I'm an important member of the CSFMB! I drive a Dodge Stratus!

_________________
"He is a loathsome, offensive brute
--yet I can't look away."

It's a Cisco 4410N.

_________________
You know me like that.

Maybe. You mean keep the 2WIRE on but stop broadcasting the 2WIRE network?

I did connect the computers to the cisco network that was being broadcast to see if that mattered and couldn't connect either way.

_________________
You know me like that.

_________________
This is my signature...

Thanks.

I'll try what you suggest. Thanks.

_________________
You know me like that.

I guess I'm confused. Is your 2WIRE the only box you have or were you provided with that box and a "cable modem" or whatever it's called for FIOS? If it's a combo box, you definitely want to turn off the wireless though that may not be your problem. If the 2WIRE is acting like it's an access point it is probably handling the routing and therefore 192.168.1.245 is not going to be found.

Does your Cisco have ethernet ports? If so, you definately should be able to get to 192.168.1.245 that way for the initial configuration.

_________________
You do not talk to me like that! I work too hard to deal with this stuff! I work too hard! I'm an important member of the CSFMB! I drive a Dodge Stratus!

The 2WIRE runs the phones, TV signal, and wireless network with 4 ethernet ports.

The Cisco has one ethernet port. I tried this a few months ago with a cheaper Netgear wireless router with an uplink port and it worked although not very well.

I've not used a WAP before. I assumed you connect the WAP via the ethernet port to the existing router and it broadcasts the signal, which it is doing.

I tried disabling the 2WIRE wireless network just now with no luck. I'm just kind of out of ideas. I tried connecting the Cisco directly to a laptop to see if it would connect, but no luck there either.

_________________
You know me like that.

Thanks again. I think you'll be sad to learn that I actually get paid to fix these kind of problems from time to time. But, I fully admit I'm far from an expert and if I never had to do it again, I would be ecstatic. I hate computer problems.

_________________
You know me like that.

Once you plug in the Cisco WAP to the 2WIRE modem/router turn everything off. Boot up the 2WIRE first and wait for all the connectivity lights. Turn off the wireless broadcasting and then turn on the Cisco WAP. It should grab a valid IP from the 2WIRE. IN the 2WIRE interface you should be able to get to an IP table that will list all the addresses it has given out. For instance on my Linksys router its under Status - Local Network - DHCP Clients Table. It should list Device Name/Ip address/MAC address from here you should be able to see what IP the Cisco WAP was given. Use that IP to get to the interface.

Also if there are 4 ports on the 2WIRE, try a different one for the Cisco WAP. Maybe its just a bad port?

Hope that helps.

_________________

OK, thanks jack. I cleared all devices and did what you suggested.

I've also ID'd that there are 3 devices on the network using Port 4 which is where the Cisco router is plugged in, one is my computer and I'm not sure what the other 2 are but none of the devices listed have an IP conflict with the CP for the Cisco so I'm not sure what can be done.

_________________
You know me like that.

Of course Darkside is gone when we actually NEED an Avaya II certified technician

_________________

So....my picture didn't help out at all? I mean, not even a little?

_________________
This is my signature...

Avaya II certified bitches

_________________

That's how I noticed the devices. They had all been on Port 2 and when I switched to Port 4, they all switched as well. I'm assuming they are the devices that are connected to the Cisco network.

_________________
You know me like that.

Does the IP address you get from the 2WIRE for the Cisco WAP differ from the default it tells you to use? For instance if it gives you 192.168.1.104 use that instead of the 192.168.1.245 to get to the WAP interface. And if 3 devices are using port 4 that is odd - the DHCP table hasn't released entries for some reason. If there is another open port I would try that. Lastly you can matchup the MAC address to the IP to make sure you have the right one. Every network device has a sticker on it with its MAC address (in this format XX-XX-XX-XX-XX-XX where X can be a number or letter) - find the one on the WAP and see what IP it matches up with in that table.

_________________

Just thought of something - in the 2WIRE interface there should be a page that allows you to adjust the range of DHCP addresses given out. Usually its 192.168.1.1 up to 192.168.1.50 - you can try to change that so the it gives out addresses up to 192.168.1.254. That way if the Cisco device is hard coded for .245 it should then be visible to the network.

_________________

Yes. I've found it. It has an IP of .67 but I can't connect that way either.

_________________
You know me like that.

It does go up to .254. I tried to assign the .67 to .245 through the 2WIRE admin panel but it just give me back an error.

_________________
You know me like that.

I think so too. I tried to Disable the firewall protection for the .67 IP but it also errored out.

I'm on the Cisco wireless network but the default gateway listed is the 2WIRE.

_________________
You know me like that.

Glad to see Darkside is still willing to help out a friend in need.

_________________
"He is a loathsome, offensive brute
--yet I can't look away."

Hmmm. This is definitely not plug and play

I wonder if the Cisco unit you have was a returned one and someone messed with the default IP. You can try to reset the device back to factory defaults (usually tells you how in the booklet that it comes with). I wish I could have been more help - Sorry Doc.

_________________

That's such a Darkside thing to say

_________________

No. I appreciate the help, Dethklok.

Let's just keep it in this thread if that's OK. Don't listen to RFDC. Nobody else does.

I'm taking a break for lunch. Thanks for all the suggestions. I think I'll tackle from a different direction after lunch. I'll keep you posted if I need more help. Thanks again.

Maybe I'll take IMU's suggestion and go back in time.

_________________
You know me like that.

That's a negative Ghost Rider

_________________

Whenever I'm in that area I like to go to a little chinese place that is absolutely dynamite. It's called PF Chang's and it's probably the best authentic chinese food I've ever had.

_________________
You do not talk to me like that! I work too hard to deal with this stuff! I work too hard! I'm an important member of the CSFMB! I drive a Dodge Stratus!

I guess it's not for everyone. Maybe you are the kind of guy who likes chains and eats at Panda Express. I like authentic chinese the best.

_________________
You do not talk to me like that! I work too hard to deal with this stuff! I work too hard! I'm an important member of the CSFMB! I drive a Dodge Stratus!