Can not connect to http//192.168.0.1

Some cases of redirecting the path are common
1. Redirect 1 single link
To redirect the individual paths as shown below

http://example.com/old-path.html => http://example.com/new-path.html
You can use 301 redirects like this:

Redirect 301 /old-path.html /new-path.html
2. Redirect the path from the old domain name to the new domain name
http://example.com/* => http://example.net/*
If you already have an old domain name like example.com, and now you have decided you really want to use example.net for the site. You can set up 301 redirects for the entire domain, so that users who access the old path can immediately be redirected to your new domain.

RewriteEngine on
RewriteCond% {HTTP_HOST} ^ example.com [NC, OR]
RewriteCond% {HTTP_HOST} ^ www.example.com [NC]
RewriteRule ^ (. *) $ Http://example.net/$1 [L, R = 301, NC]
3. Redirect the link from www to non-www
http://www.vinasupport.com/* => http://vinasupport.com/*
A search engine like Google will see example.com and www.example.com, which are basically two separate websites. They recommend that you choose a category you want the search engine to display and use 301 redirects to redirect to one.

To redirect the path from www to non-www in htaccess you can do the following:

RewriteEngine on
RewriteCond% {HTTP_HOST} ^ www.vinasupport.com [NC]
RewriteRule ^ (. *) $ Http://vinasupport.com/$1 [L, R = 301, NC]
4. Redirect the path from http to https
http://vinasupport.com/* => https://vinasupport.com/*
Chrome and Firefox have begun displaying unsafe warnings on websites without SSL certificates. Without SSL, your site will appear unsafe for visitors. Therefore, use an SSL encrypted connection for security reasons. Redirecting from HTTP to HTTPS is very important.

To navigate the website to https we can do the following:

RewriteEngine On
RewriteCond% {SERVER_PORT} 80
RewriteRule ^ (. *) $ Https://vinasupport.com/$1 [R, L]

There is probably a reset button somewhere on the device, it is probably a small pinhole that you put a paper-clip into the reset.
If it has its own http web page, there is likely a reset to factory defualts option.

The ip of the computer connecting to it should not change.
On a computer connected to it, open cmd start>run then type in cmd, and type 'ipconfig'.
It will display details about your connection. Where it says 'default gateway' is the ip of the device.
You could try to put the ip in your browser and see if the device has a web page.

For that Connect your router to computer with ethernet cable then you can access it with following default link.

For belkin router http://192.168.15.1
or
http://192.168.2.1

If you are not able to access it with above ip then check your computers ip address gateway ip is your router ip try with it.
Then it ask for user name and password.
Type user as "admin" and password as "admin" or "password" or blank.
Then you can see configuration page of router.
Click on wireless settings then WEP Security then add WEP code .It is your password to connect wi fi.Then save settings and restart router.
Then you can connect your wi fi network with that code.
If your password showing in * or # format then add new password with above method.
Let me know if you need further assistance.
Thanks for using FixYa.

you need to replace your modem with a router that is capable of running Network Address Translation. You are trying to route private IP's (192,168.x.x) over the public IP (internet) network.

I don't think it is a browser problem.

This may sound scary but do the following
- go to http://www.facebook.com/editapps.php

- click on the X next to farmville

- application removed, click OK

- go to farmville application again, it will ask for access again, click allow

- You will be back to your farm as you left it and no redirecting problems.....

You cannot configure the DLink by the URL address http://dlinkap?
You connect a LAN cable from your computer to the DLink.
Then open Internet Explorer and enter the URL http://192.168.0.1
the default login = admin
the PW is blank (just press Enter)
You can now configure the DLink.

That is the default site for facebook. Facebook automatically redirects you to that directory of their site.

Introduction
Your Web server thinks that your URL has been temporarily redirected to another URL. The client system is expected to immediately retry the alternate URL.
302 errors in the HTTP cycle
Any client (e.g. your Web browser or our CheckUpDown robot) goes through the following cycle when it communicates with your Web server:

• Obtain an IP address from the IP name of your site (your site URL without the leading 'http://'). This lookup (conversion of IP name to IP address) is provided by domain name servers (DNSs).
• Open an IP socket connection to that IP address.
• Write an HTTP data stream through that socket.
• Receive an HTTP data stream back from your Web server in response. This data stream contains status codes whose values are determined by the HTTP protocol. Parse this data stream for status codes and other useful information.

This error occurs in the final step above when the client receives an HTTP status code that it recognises as '302'.
Resolving 302 errors - general
The 302 response from your Web server should always include an alternative URL to which redirection should occur. If it does, a Web browser will immediately retry the alternative URL. So you never actually see a 302 error in a Web browser, unless perhaps you have a corrupt redirection chain e.g. URL A redirects to URL B which in turn redirects back to URL A. If your client is not a Web browser, it should behave in the same way as a Web browser i.e. immediately retry the alternative URL.
If the Web server does not return an alternative URL with the 302 response, then either the Web server sofware itself is defective or your Webmaster has not set up the URL redirection correctly.
Resolving 302 errors - CheckUpDown
Redirection of URLs may occur for low-level URLs (specific URLs within your Web site such as www.isp.com/products/index.html) when you reorganise your web site, but is relatively uncommon for the top-level URLs (such as www.isp.com) which most CheckUpDown users ask us to check. So this error should be fairly infrequent.
The 302 response from your Web server should always include an alternative URL to which redirection should occur. If it does, CheckUpDown automatically tries the alternative URL. This in turn may possibly lead to another redirection which CheckUpDown then tries. This continues for a maximum of 5 redirections. As soon as 5 redirections have occurred, CheckUpDown gives up and reports the 302 error for your account. So you should only ever see the 302 error if 1) your Web server gives no alternative URL on the 302 response or 2) the number of redirections exceeds 5. This second condition should be fairly unlikely - and may indicate a recursive pattern e.g. URL A redirects to URL B which in turn redirects back to URL A.
You first need to check that the IP name we use to check for your account is accurate. If you or your ISP have configured something so that any access using this name should now be redirected to another name, then you need to update your CheckUpDown account to start using the new name.
If you believe that the IP name we use is exact (should not be redirected), please try accessing the current URL using a Web browser. Note carefully which URL actually gets displayed, because your browser may silently switch to a substitute URL if it receives an 302 message from your Web server. If you see any evidence of a new URL, try accessing that directly from your browser. If this works (you see your Web site as expected), then this new URL is what you may need to update on your CheckUpDwon account. If this is a temporary redirection, then you may also need to reinstate the original IP name at a later date when the redirection is no longer effective.
If none of the above help, we can analyse the underlying HTTP data streams we receive from your Web server. These can provide additional information about the new URL(s) which your Web server thinks we should be accessing. Before doing this, we prefer you to identify any deliberate changes on your side, liaising with your ISP if needs be.
302 errors should occur infrequently, because top-level URLs do not change often. If they do change, then this is typically because a redirection URL is being suggested. This pervasive change is unlikely to occur by accident, so most often we can resolve this error by updating our system records for your account following a deliberate change of URL on your part, whether this change is temporary or permanent.

hi thanks for using fixya!!

Try to update your windows, and your browser. Perhaps, you are havinng slow internet connection.

If you need further assistance, let me know.

Alright, here's a FixYa if I've ever done one. We use a couple of products. This one will tend to knock your socks off, if you only need a single antenna. www.open-mesh.com $50 gets you a wireless router that will do splash screen and redirect. For each element of $50 you can add units. They tend to be private, so if you're gaming via wireless, it's going to be difficult to share the network.

Give it a try.

Carl