Hi niik, welcome to DaniWeb
I can think of at least a couple of reasons that you can't reach Internet sites through that connection:
1. The network is not secured with encryption or a password, but Internet access
is controlled by a proxy server on the network... good luck hacking past that.
2. The DHCP server on the network is assigning your computer a valid IP, but isn't passing you DNS server IPs. You can verify this by doing these steps while connected to the network in question:
* Try reaching a site by its actual IP address instead of its URL. For example, open a browser and enter the following in the address/location bar:
http://66.102.7.99
If that takes you to Google, chances are pretty good that you've got a DNS problem.
* Click on the "Run..." option in your Start menu. In the "Open:" box of the resulting window, type "cmd" (omit the quotes) and hit Enter. This will bring up a DOS window.
At the DOS prompt, type the following commands, hit Enter after each, and tell us the results for each command (if DNS is working properly, you should receive 4 positive responses from Google, followed by some summary info):
ping 66.102.7.99
ping www.google.com
* Again at the DOS prompt, type the following command and hit Enter. You won't see any result from the command, but when it completes, a second prompt with a flashing cursor will be displayed; close the DOS box once that happens:
ipconfig /all >ipconfig.txt
The above command will have created a text file on you desktop named ipconfig.txt; double-click on the file to open it in Notepad, and then cut-n-paste the file's contents in your next post here. The contents of the file will give us some important details of your IP configuration.
iv read somewhere about ip address' begining w/ 192.168.25 (which is the address i get) arent real or something for protection
There are 3 IP address ranges which have been reserved for use on private networks only, and the range of 192.168.0.
x through 192.168.255.
x is one of those. "Reserved" or "private" IPs are definitely valid, but they can only be used on LANs like a corporate network or your home network; they cannot be directly routed to/from the "outside world" of the Internet. This
isn't done primarilly for security reasons, but more as a way to keep from depleting the entire pool of available IP addresses. If every single network-capable electronic device on the planet had to have its own unique IP address, under the traditional Internet addressing scheme (IP v.4) we would have run out of unique IPs already. The idea of having non-unique "private" addresses which could be used on any number of separate networks at the time was developed as a way to hold off that inevitable event. IP v6 (when it comes into widespread use) will alleviate the problem for some time by greatly expanding the total number of available IP addresses.
(Networking Fun-Fact # 1024:
Occasionally, network packets which carry reserved IPs as their supposed source IP address
do manage to appear out on to the Internet. Internet routing devices know that such packets are invalid/erroneous/bogus for Internet transmission, and the term they use for them is "Martians". It's kind of amusing to look through router activity logs and see entries referring to things like "Martian transmissions" or "Warning- Martian source detected!".)