Possible Networking Sticky

[bored28]

Admins, Moderators, and members....

I've had an idea here in the past few days. Would anyone be in favor of maybe applying a sticky to the Networking section which could basically go through the most common work-arounds for networking problems?

I think it would really benefit the community if there was a first-stop sticky where people could go through the most common procedures to see if their problems can be fixed there. For example, the first and foremost thing that has fixed several visitor's issues is the good 'ol "restart every device" procedure. This works for so many problems because a lot of people do not realize how finicky routers can be with NAT entries and the like.

Another idea is that it should tell them to include certain information when posting in this section because using logs, MAC address, IP addresss, subnet masks, etc can all be vital in determining the problem.

This just a thought that could possibly make the Networking section more efficient. If people do think this is a good idea, then we should discuss the contents of that sticky so that we can cover what is deemed the most common problems. Obviosuly some problems are just too complex and user-specific to be fixed by a sticky, however; the sticky can help filter these requests appropriately.

Yea or Nay ? :)

[yellow]

Moved to site feedback section.

[hayne]

I think it is a good idea to have such a "sticky" thread with answers to common questions.
NovaScotian suggested this sort of thing previously in this post:
http://forums.macosxhints.com/showpost.php?p=279110&postcount=13

Please suggest a list of possible topics to be covered here and maybe eventually we can get around to creating such a FAQ for networking issues.

[bored28]

Geez, where to begin.. i think first and foremost, a clean restart of all devices is essential. Also, it may not be a bad idea for every person to reset their devices settings back to the facotry defaults. This way, everyone starts from the same relative position.

[tbsingleton73]

1. Turn off ALL Devices.
2. Turn back in following order (modem, router, others, computers, other others)
3. Update Firmware on devices if available (check firmware notes as it may mention fix to your issue).
4. Reset to Factory Default via software or Hard Reset button.
5. Turn off All Security if required to troubleshoot.
6. Re-enable security one at a time to see if issue returns.
7. Confirm hardware actually working...try on different computer, replace with other same hardware, etc, etc.
8. Test Connection for each "bridge" with ping to find the "bridge" that is down.
#. If no internet connection, determine if connection (Web Interface Page) works on Router from computer. Indicates issue between router and modem and internet, NOT computer to router.
#. Avoid Internet Connection Sharing, use a Router, that's what its for.
#. If websites not working, check DNS working or configured properly.
#. Intermitent Wireless usually indication of Signal Congesstion or Interference.
#. Try to keep wireless channel at least 4 channels from other wireless networks.
#. If the network equipment cost less then your lunch at McDonald's, don't be so cheap, get a quality brand, known product, stick with the top 3-4 (Linksys, DLink, Netgear, etc).
#. USB wireless and Mac's don't mix, avoid if possible.
#. Wirless keys entered on Macs sometimes need to be in "quotes" or preceded by the $ symbol. (ex. "12345" or $12345)
#. WEP sucks, use only if older hardware doesn't allow WPA or WPA2
#. Delete the prefered network entry or SSID on computer and recreate the connection.
#. Sometime the old keychain stays and is not replaced by a new one. Delete the entry in the keychain for the SSID Network and recreate.
#. The signal bar for wireless on the menu bar by the clock is not very accurate, use a program like iStumbler to see signal strength.
#. Maybe it's just broken. Just because it worked yesterday doesn't mean it is today. GO BUY A NEW ONE.
#. In high signal congestion area moving to "A" band 5.4GHz wireless will avoid the issues with the 2.4GHz frequency range. But Mac's don't do "A" band. More for Windows computers.
#. Get some sleep, networking and wireless issues can be the death of you.
#. Go back to the top steps, I'm sure you skipped something because you felt you didn't need to do them.
#. When fixed, consume lots of your favorite alcoholic beverage. Must be of legal drinking age.
#. NEW - Computers with different scopes of IP Addresses can NOT "see" each other. Ensure they are all on the same scope. Example. Computer on 192.168.2.1 can see computer at 192.168.1.1
The first three groups must be the same (192.168.1.x)

[bored28]

Nice..... i'm making a few additions myself.. will post in a few...

[Craig R. Arko]

Sounds like a plan; I'll see if I can think up some as well. :)

[CAlvarez]

In high signal congestion area moving to "A" band 5.4GHz wireless will avoid the issues with the 2.4GHz frequency range. But Mac's don't do "A" band. More for Windows computers.
All of the Intel-based Macs have 802.11a built in.

An addition:

Network Utility is your friend. It will tell you if you have an IP address, and give you more useful error messages by using the "ping" and "lookup" functions.

[hayne]

All of the Intel-based Macs have 802.11a built in.

It's true that it's built into the hardware but I recall reading somewhere quite recently that it isn't supported in software. I think I read this in Apple's developer note on the MacBook.

I looked up the developer notes for the MacBook & MacBook Pro and they both contain this:

Note: Although the AirPort Extreme module contains 802.11b, 802.11g, and 802.11a radios, Apple supports only 802.11b and 802.11g.


Do you have any experience in successfully connecting to an 802.11a network with an Intel Mac?

[tbsingleton73]

Network Utility is your friend. It will tell you if you have an IP address, and give you more useful error messages by using the "ping" and "lookup" functions.
Yes, true. But, in giving basic directions to someone who doesn't know anything about networks, asking them to just open Terminal and type "ping name.com" and what are the results seemed quicker then asking them to open Network Utility, go to the ping tab, type the name press the ping button, etc.
Granted its only a few more steps, but was keeping it as KISS as possible.
Your way works too.

[yellow]

#. NEW - Computers with different scopes of IP Addresses can NOT "see" each other. Ensure they are all on the same scope. Example. Computer on 192.168.2.1 can see computer at 192.168.1.1
The first three groups must be the same (192.168.1.x)

Might want to specify exactly what you mean by "see" each other. I can definitely connect to other computers outside my subnet. I can also ping them to "see" them.

[tbsingleton73]

My "see" was jsut that being able to network to them or ping them.
My experience shows that a computer on 192.168.1.2 cannot see a computer at 192.168.2.2 but can see one on 192.168.1.3.
But maybe there was something different than that too.

[yellow]

Ah.. well that's probably because there's a hardware firewall in the routers between the private networks that is blocking such activity. So, I suggest amending that entry specifying "private networks", as what you said is true unless specifically planned for within such a network.

But I can assure you, I can definitely ping and network to boxes outside my subdomain, or even domain. :)

[tbsingleton73]

Yes, correct. I would be referring to a private network.