With wireless, there are two parts to getting everything to communicate. There's a radio (wireless) side, and an IP (Internet) side. You have to have the radio side correctly configured before you tackle the IP side. For the wireless side, you need to know the following information before the radio in your network card will communicate with the radio in the router:
1) The name of the wireless network (SSID).
2) The channel used by the radios.
3) The mode that the router is working in.
4) What, if any, security mechanism is in place.
4-a) The security key authentication type
4-b) The security key encryption strength.
Depending on how your friend has the wireless part of his network configured, his router may have been providing you with #1 and #2. If your computer searched for a network and found "bob's network" on channel "4", then that's a start. If your computer simply found " " on channel "4" then his router isn't broadcasting the name of his network and you need to enter that information into your wireless card's configuratoin utility. For #3, the options are 802.11/b, 802.11/g, or both. Most often the router is set to serve both, so that shouldn't have been a problem. But it's something to check if things aren't working.
Once you've got the wireless SSID and channel, you need to handle the encryption part. If your friend's network is not encrypted, you should have been able to connect to it. Some light on the card may have stopped blinking and gone solid, perhaps an icon on your desktop went from red to green, or something similar.
If his network is encrypted, then you need to know the type of encryption used, the length of the key, and the actual key used. The type of encryption is most likely WEP, but could be WPA-PSK if he's really on top of security issues. A WEP key can be one of two lengths, either 64 bit or 128 bit. A WPA-PSK key is generated by entering a pass-phrase (Some routers let you use a pass-phrase for WEP as well). You may have to type in (or select) the encryption type, key length, and key value into your wireless card's configuration utility.
If you've entered all of the information and you still can't connect to his network, then there are a few other things to check on the router side. His router may be configured to only allow wireless network cards with a particular physical address, called a MAC address. Every network card made has a unique address assigned to it. Think of it as a fingerprint. The router may have a list of trusted network cards and only they are allowed access to the network.
If you've reached this point and you're connected to his wireless network, you're half-way home. You still need to fix the IP side of the equation. You need an IP address, subnet mask, network gateway, and a couple of domain-name server addresses. His router is most likely set up to send your computer this information. One way to check this is to open up a console window or command prompt (not sure which version of Windows you're using) and type the command "ipconfig /all". It will list the above information, if it has been provided. In particular, make sure values have been set for: (examples in parentheses)
Make sure the first three sets of digits (192.168.0) for IP Address, Default Gateway, and DHCP Server match the first three sets of digits of your friend's network. Windows sometimes caches these values and uses them even if your computer is trying to use another network. If any of the above information is missing or does not match your friend's network then you've found the problem. Getting things to work at this point depends on what version of Windows you're using.
From your description of the problem, it sounds like the last paragraph is where your problems lie. The wireless part is probably fine. My guess is that the router isn't providing you with domain-name servers, or that your machine is trying to used cached (stale) information from a network that isn't your friend's. Your computer can't find a server to translate domain names (www.garageglamour.com
) to physical internet addresses (188.8.131.52). That's why you can't get your browser or email client to work.