If this is your first visit, be sure to check out the FAQ by clicking the link above.
You may have to register before you can post: click the register link above to proceed.
To start viewing messages, select the forum that you want to visit from the selection below.
My wireless router does not work with DHCP anymore. When I have the computer set to obtain IP auto, it gives me an IP of 192.168.0.xxx with a gateway of 192.168.1.1. Anyone know whats going on?
Contacted Linksys and their fix was to set static IP, which is fine. But when I have friends come over with their computers, its more of a pain in the ass to setup static. My next question is there a freeware program that shows you what IP's are being used on the network? I remember one that showed open IP's in green and used IP's in red...Any ideas?
__________________ Life is not a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside, thoroughly used up, totally worn out, and loudly proclaiming -- "WOW--what a Ride!"
Doesn't the 192.168.0 for IP have to match the 192.168.21 for the gateway? What screen shots would be helpful? The IP screen?
__________________ Life is not a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside, thoroughly used up, totally worn out, and loudly proclaiming -- "WOW--what a Ride!"
if you go to your routers IP address in your web browser and go to the status page, LAN, you will find a dhcp client table.
I'm not understanding your issue. If you are getting a 192 address that should be correct. If your router's address is default 192.168.1.1 then the address that should be given out is 192.168.1.x
__________________ Car ~ 2003 Honda S2000 - Stock - Black - 9K RPM
BEATER ~ 1992 Honda Civic LX ~ *fixed* axle, Bad Idle, Burnt 4th Gear Synchro - White
Bike ~ 2007 Kawasaki ZZR600 - Black
Goodies - Yoshi can, K&N Filter, DynoJet Stage 1 Jet Kit, Factory Pro Ignition Advancer, Galfer Brake Lines, Flush mounts, Swingarm Sliders, Pazzo Levers, Grip warmers, n CarbonFreak Windscreen 99.63 WHP
if you go to your routers IP address in your web browser and go to the status page, LAN, you will find a dhcp client table.
I'm not understanding your issue. If you are getting a 192 address that should be correct. If your router's address is default 192.168.1.1 then the address that should be given out is 192.168.1.x
My issue is that I am getting different router ID numbers. One is giving me a 0.xxx and one is giving me a 1.xxx. They dont match up.
__________________ Life is not a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside, thoroughly used up, totally worn out, and loudly proclaiming -- "WOW--what a Ride!"
For example, sometimes I get an IP of 192.168.1.101 and a gateway of 192.168.0.1. Then other times I get an IP of 192.168.0.101 and a gateway of 192.168.1.1
__________________ Life is not a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside, thoroughly used up, totally worn out, and loudly proclaiming -- "WOW--what a Ride!"
if you go to your routers IP address in your web browser and go to the status page, LAN, you will find a dhcp client table.
But when you have assigned IP's, it doesn't show up in the DHCP table
__________________ Life is not a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside, thoroughly used up, totally worn out, and loudly proclaiming -- "WOW--what a Ride!"
Static assignments should also show up in the table. Unless the table is just for dynamic IPs.
The table is labeled DHCP table, so I thinnk only DHCP assigned IP's would show up.
For the screen shot, I will try to VNC into my server and get something up in a little bit.
__________________ Life is not a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside, thoroughly used up, totally worn out, and loudly proclaiming -- "WOW--what a Ride!"
__________________ Life is not a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside, thoroughly used up, totally worn out, and loudly proclaiming -- "WOW--what a Ride!"
Ok, first of all, 192.168.1.xxx is a class c network, which means the first three octets (192.168.1) must be the same, or they are not on the same network, and will never be able to talk to a gateway with 192.168.0.xxx, or vice versa. If you go into the status tab of your router, it should have a lan ip table, like the others said, and should also show statics. However, if you havent already, I would upgrade (or reinstall) the firmware, and reset the router.
__________________
A smoking hole is a small price to pay for a sh!t hot maneuver!
Yes, that is why I cannot work on he network when it gives me either a 0.xxx IP or a 0.1 fgateway. That's what the problem is. I will try the updating firmware and resetting the router when I get home
__________________ Life is not a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside, thoroughly used up, totally worn out, and loudly proclaiming -- "WOW--what a Ride!"
BTW, the DHCP client that is listed is my print server, which has worked flawlessly on DHCP for years, and is continueing to do so. I have 2 other wired connections (w/ static IP) and 2 wireless (w/ static) right now on the network
__________________ Life is not a journey to the grave with the intention of arriving safely in a pretty and well preserved body, but rather to skid in broadside, thoroughly used up, totally worn out, and loudly proclaiming -- "WOW--what a Ride!"