can not log into my routers homepage from iMac

Are you using a slightly older version of Safari? There was an issue where Safari couldn't log in to certain routers, which has since been fixed. You could test this by trying it in Firefox or Chrome, or updating your Safari to the latest version.

Have you tried connecting to the router via wire or via air?

Maybe try the opposite of what you have done. Via wire has been working for me most of the time, when I tried to connect to my router.

ilonkapav said:

Safari says - Safari can’t open the page “http://www.192.168.1.1/” because Safari can’t find the server “http://www.192.168.1.1”

Click to expand...

How about trying http://192.168.1.1 and leave off the 'www' part?

I believe Safari will add a www. if it can't find an address, but I wouldn't expect it to do that with an IP address under any circumstances, and I've never had it do that to me. (Indeed, I just checked, and it doesn't.)

Just to confirm something, try opening up System Preferences -> Network and selecting whichever connection you are connected via.

What do the "IP Address" and "Subnet Mask" entries say? (If the IP address doesn't start with 192.168, you needn't post the last two sets of numbers on it if you're worried about security for any reason.)

You already have the latest version of Safari, but you also hadn't said if you'd tried downloading Firefox or Camino and trying one of those--it'd only take a moment, and that would narrow it down considerably if something other than Safari works.

Makosuke said:

(If the IP address doesn't start with 192.168, you needn't post the last two sets of numbers on it if you're worried about security for any reason.)

Click to expand...

Doesn't matter. Addresses that begin with 192.168.*.* are private addresses, not public.

What model is the router? VM supply a few different ones and they don't all use the same IP address for the admin page. eg the dlink ones use 192.168.0.1 by default

Have u tried downloading Firefox and using that?

-J.-

miles01110 said:

Doesn't matter. Addresses that begin with 192.168.*.* are private addresses, not public.

Click to expand...

That's why I said it wasn't necessary to post more than the first two blocks if it wasn't in the private space, since it wouldn't matter anyway at that point, while if it is in the private space it's not a security concern and necessary to see the other half to determine if it's in the same subnet. Maybe my double-negative wasn't clear.

You probably figured this out, but I'm trying to determine if the router is either giving the OP an IP address in a block other than expected (and different from the address in question), or if it's in bridge mode or otherwise passing an external address, which would of course explain why an internal address wouldn't respond.

I just spent an annoying amount of time configuring a bridged range extender due to an issue like this--when operating properly, the computer on its network would get an external IP address, but if it didn't work the default address of the device was on a different subnet.

Makosuke said:

That's why I said it wasn't necessary to post more than the first two blocks if it wasn't in the private space, since it wouldn't matter anyway at that point, while if it is in the private space it's not a security concern and necessary to see the other half to determine if it's in the same subnet. Maybe my double-negative wasn't clear.

Click to expand...

Oh, yeah sorry- I totally read that wrong.