View Single Post
Old May 12, 2008, 11:39 PM   #7 (permalink)
Tipstaff
DriverHeaven Extreme Member
 
Tipstaff's Avatar
 
Join Date: Jul 2002
Location: 3rd Captial of Canada, Igloo City
Posts: 4,692
Tipstaff is a glorious beacon of lightTipstaff is a glorious beacon of lightTipstaff is a glorious beacon of lightTipstaff is a glorious beacon of lightTipstaff is a glorious beacon of lightTipstaff is a glorious beacon of light
System Specs

It suddenly dawned on me, but I think the problem is that you are running 2 different levels of IPs. In this case your network is running most likely off of 192.168.178.xxx, yet your Access Point is running 192.168.0.xxx. Sometimes this should not effect things, but other times I've seen networks completely bork, and not work at all. So, here's a couple things to try (it's also best to do these things hooked up to your router by wire, not wireless as you could run into a lot of issues):

1) Set a static IP address for your computer that is within range of your your APs IP. For instance, try setting a static address of 192.168.0.100, with a subnet of 255.255.255.0. Don't worry about putting in a Gateway or Primary/Secondary DNS address as it's not necessary at this point. Then, try connecting to your AP.

2) Since you can get into your router you may want to consider changing it's default 192.168.178.1 address to be in line with your APs addresses, in this case you could do 192.168.0.1. This would also change the IP range it dishes out for DHCP to be within your APs range as well, in which case any computer running on DHCP would be "technically" on the same network now as your AP.
__________________



>><<
Tipstaff is offline   Reply With Quote