|
|

21-03-2008, 02:51 PM
|
|
Ex-InGenius :p
Group: Regulars
Location: 30km from Perth - in my first ever own home (nearly)
|
Ok, have you tried the reboot option that I suggested? All off (computers & router) > Router on > Mac on - leaving the PC's off.
I think the next step is to check the router configuration is set up to lease out more than 2 IP addresses. If possible (I don't know the D-LInk that well) check to see how many clients are connecting to the router from the configuration screen.
You might want to try turning Airport off in the menu and then turning it back on... I've got a sneaky feeling I've seen this before.
__________________
iPhone v1.1.3, Macbook C2D 2ghz. iMac alu. 20" C2D 2ghz. iMac 20" CD 2ghz & Cube 450mhz.
Bisho's blog Thoughts and musings of a bored person
Flickr - updated regularly
Older photo's - here
|
|
|
|
|
|
|
|

21-03-2008, 02:52 PM
|
|
Clinically Insane
Group: Regulars
Location: Sydney, Australia
|
Okay - go back into the TCP/IP window, and click in Using DHCP and scroll it down to: Manually.
In the IPv4 Panel, type: 192.168.0.5
Subnet Mask: 255.255.255.0
And leave Router as: 192.168.0.1
Click once on the OK button, and the once on the Apply button back in the Network window and then Quit System Preferences.
If it does not work immediately, try shutting down the MacBook, shutting down the D-Link Router - (pull out its Power Cord) for 30 seconds - then plug the Router's Power back in, wait for its lights to stabilize again, and then turn on your MacBook.
|
|
|
|
|
|
|
|

21-03-2008, 03:17 PM
|
|
Member
Group: Member
Location: Melbourne
|
Quote:
Originally Posted by decryption
A 169 range IP address means it is not receiving a DHCP lease from the router.
You may be having problems connecting to the access point itself. When you connected to the access point, did you enter in a password?
|
there is a password for the network if thats what you mean? its one of the trusted networks so it doesnt prompt for a password everytime
|
|
|
|
|
|
|
|

21-03-2008, 03:38 PM
|
|
Member
Group: Member
Location: Melbourne
|
ok clockwork and lutze i have tried both your methods (thank you for your help so far also) and to no avail. Im heading over to a friends later who has a big external hard drive and leopard/cs3 etc, so i think i might completely format the computer then re install and start over. Is this in vein or do you think it could do something?
|
|
|
|
|
|
|
|

21-03-2008, 03:44 PM
|
|
Clinically Insane
Group: Regulars
Location: Sydney, Australia
|
I don't think you have to go THAT far !
Is the light symbol next to AirPort in Network, orange or green ?
What happens if you restart the connection process by connecting it back to Ethernet...
(Start back with connecting an Ethernet Cable. With the last method that worked - in other words).
sometimes, cracking a other people's problems in a forum is difficult - depending on what kind of feed back the OP gives us... there are not always immediate solutions...
|
|
|
|
|
|
|
|

21-03-2008, 03:47 PM
|
|
Regular
Group: Regulars
Location: Darwin
|
I had this trouble with my brother in laws machine. Turned out that the router was configures as an open access point and OS X wouldn't pick up an IP address, Reconfigured the access point with WPA2/PSK and all was good. Except you would have to reconnect the other machines on your network
__________________
C2D MBP 15.4" 2.53GHz
iPhone 16GB
٩๏̯͡๏)۶ LINUX: Fedora 9
|
|
|
|
|
|
|
|

21-03-2008, 04:01 PM
|
|
Member
Group: Member
Location: Melbourne
|
Quote:
Originally Posted by ClockWork
I don't think you have to go THAT far !
Is the light symbol next to AirPort in Network, orange or green ?
What happens if you restart the connection process by connecting it back to Ethernet...
(Start back with connecting an Ethernet Cable. With the last method that worked - in other words).
sometimes, cracking a other people's problems in a forum is difficult - depending on what kind of feed back the OP gives us... there are not always immediate solutions...
|
well it has been 2 different things, when it displays 'no ip address' the light is orange, and when i renew dhcp or enter in the numbers manually it says self assigned ip and the light is green. Im typing this on my mac with the ethernet in (in network both ethernet and airport have green lights with ethernet on top) and once i take out the ethernet it goes red, airport remains green and the problem persists.
|
|
|
|
|
|
|
|

21-03-2008, 04:05 PM
|
|
Regular
Group: Regulars
Location: Darwin
|
Quote:
Originally Posted by nickv
well it has been 2 different things, when it displays 'no ip address' the light is orange, and when i renew dhcp or enter in the numbers manually it says self assigned ip and the light is green. Im typing this on my mac with the ethernet in (in network both ethernet and airport have green lights with ethernet on top) and once i take out the ethernet it goes red, airport remains green and the problem persists.
|
That's what was happening with my brother in laws machine (see above) ethernet worked but wireless was getting a self assigned address. Check that the wireless is configured with security turned on.
__________________
C2D MBP 15.4" 2.53GHz
iPhone 16GB
٩๏̯͡๏)۶ LINUX: Fedora 9
|
|
|
|
|
|
|
|

21-03-2008, 04:12 PM
|
|
Clinically Insane
Group: Regulars
Location: Sydney, Australia
|
Quote:
Originally Posted by nickv
modem ip is 192.168.0.100 i think but there is nothing listed next to router
|
If the Router's IP is indeed: 192.168.0.100 (and therefore ends in: 0.100) - then the IPv4 Panel needs to go to a higher number than 0.100 - eg: 0.103 - or 0.108 - or 0.112
on the D-Link page though, it claims that the DI-624's IP Address is 192.168.0.1, as seen here.
Might be v worthwhile looking at this page - and yes, I agree with others that it has something to do with the DI-624's settings and not your MacBook.
|
|
|
|
|
|
|
|

21-03-2008, 04:38 PM
|
|
Member
Group: Member
Location: Melbourne
|
Quote:
Originally Posted by mab
I had this trouble with my brother in laws machine. Turned out that the router was configures as an open access point and OS X wouldn't pick up an IP address, Reconfigured the access point with WPA2/PSK and all was good. Except you would have to reconnect the other machines on your network
|
okay so ive done this and it worked, my mac is now working wirelessly again. thank you., but now there is 2 other computers on the network, the main computer that the router is connected to has internet connection but the other pc laptop on wireless doesnt, how did you fix that problem?
|
|
|
|
|
|
|
|

21-03-2008, 05:19 PM
|
|
Member
Group: Member
Location: Melbourne
|
ignore the last post, its all working now. we changed it to wep2 and only the mac would work so went back to wep and now all the computers are working again. not sure how that happened, just happy that its all going. big thanks to everyone that offered assistance!
|
|
|
|
|
|
|
|

31-03-2008, 08:15 PM
|
|
Member
Group: Member
Location: Perth, WA
|
Similar Problem
Hi
I've just bought a MacBook and am having problems with it connecting to the wireless network. I took it to my Mac friends house and she could not get it to connect to her network at all - even putting in all the same configurations as hers.
At first at home it would not find the home network (it found everyone elses in the street) but I can connect it by going to Network Diagnostics in Safari. It's just that everytime I shut it down or put it to sleep it won't find it again when it wakes up. I have to do the Network Diagnostics in Safari and enter the WEP password again - I can't get it to work any other way.
I have connected other Macs before that I brought home from work and we have a PC on the network as well.
The thing is that we have the same Wireless router (DL-624) as Nickv and i don't know how to reconfigure the access point. Is this where Nickv changed the setting that enabled his to work? Can anyone help me?
|
|
|
|
|
|
|
|

20-06-2008, 04:57 PM
|
|
Member
Group: Member
Location: Barcelona
|
configd
Quote:
Originally Posted by nickv
ok so its set to using DHCP, then it lists this:
IPv4 Address: 169.254.41.5
Subnet Mask: 255.255.0.0
Router: *blank*
the modem ip is 192.168.0.100 i think but there is nothing listed next to router
|
I cant tell you what the problem is, but I can tell you one sympton, maybe that will help:
When your Subnet Mask will show 255.255.255.0, then the same IPv4 address will work.
I am having the same issue everytime I try to connect to my home wifi. I get Subnet Mask: 255.255.0.0 until a message pops up asking for permition to run "application configd" and when I allow that, it goes to Subnet mask Subnet Mask: 255.255.255.0 and I can connect.
the IP address is always the same.
Problem is, I dont know how to promp "Application configd", all I can do is restart the modem, the comp, run the assistant etc until this happens. I cannot tell you how irritated I get with that...
hope this helps! And if someone can solve our problem, greatly appreciated!
R
|
|
|
|
|
|