I have a similar problem with a network drive that is over ethernet on 10.6.x
If the folder has a list of image files that approach 3000 or over, it will slow down the finder.i.e constant beach balling. The only solution is to break the files down into sub folders that have no more than 2000 file each. I also make sure that Calculate all sizes is not on or icon preview.
The problem seems to be that the finder is waiting for the ethernet to return the data but is not getting it quickly enough so beach balls. Simliar to when you try and mount a share that is not on the network anymore.
I suspect it is actually not the finder but the ethernet component on 10.6 that cannot handle either the number of items or the overall data size of the list.
The main thing that looks odd from the setup that you've mentioned above is the DNS server. It appears that the IP address your computer has allocated is being assigned as the DNS server? If you're not running DNS services on your computer, this won't work very well.
Try to remove the single DNS server (i.e., your computer's IP address) from the list of DNS servers, and see if the machine populates that list with other entries (that were potentially provided via DHCP). If there are no DNS servers listed in that dialog box after you remove the single entry, I'd suspect configuration problems on your network.
Alternately, it may help to manually configure that network interface to use Google's open DNS servers (8.8.8.8, 8.8.4.4) to see if they will respond correctly to DNS lookups.
You can use the Network Utility program at /Applications/Utilities to perform further network troubleshooting. For example, it should be possible to "ping" the DNS server, router (gateway) and some outside host from where you are. This lets you know that your machine can communicate with those devices. First, I'd recommend trying to use Network Utility to ping the DNS servers that are being provided via DHCP. Under the "Ping" tab, you can enter the IP address of each of those hosts, and click "Ping" to see if you get a response. If all of the DNS servers are responding to pings, see if you can ping the gateway (10.58.204.1). If you receive responses for pings to all of the 'internal' hosts, see if you can ping some outside host (gmail.com?) to see if your computer's network traffic is being routed to the Internet.
If all of the ping tests are passing, I'd recommend trying to perform DNS lookups on the servers that are showing up in the DNS table in Network System Preferences. You can use the Network Utility program to perform lookups, but it may be more helpful to diagnose the DNS servers individually using 'nslookup' through the Terminal program. Open Terminal from /Applications/Utilities. When the program opens, you'll see a command prompt. Type in the following queries, and observe whether or not you receive valid responses from all of the DNS servers provided:
nslookup gmail.com 172.16.2.5
nslookup gmail.com 172.18.82.11
nslookup gmail.com 4.2.2.2
Those servers should respond with some answer (and IP address for gmail.com) within milliseconds. If you're seeing the commands hang for excessively long periods, that particular DNS server may not be responding correctly.
It's odd that you're having intermittent issues when using Google's DNS servers...If you're on some larger private network (as it appears you are based on the private addresses being provided), it's possible that traffic is being filtered.
Lastly, the Awarenet profile that you're using is simply utilized for authentication to a wireless access point named "Awarenet" that uses 802.1x (WPA Enterprise) security to authenticate users (you're signing in as egoodwin). If you no longer use/join a Wi-Fi network named "Awarenet" (for work, or school?), the profile can likely be deleted.
Best Answer
Couple of different ways to fix this. First, and probably the best as it doesn't involve any hacks is:
Apple has some nice looking pictures and instructions of the above here.
If that doesn't work for you, there is a UNIX hack you can use.
In /Library/LaunchDaemons, create a file called "com.example.airport.plist" containing the following code:
This tells it to run the script /Users/YOURUSERNAMEHERE/bin/join-wifi.sh at start-up. Obviously, replace YOURUSERNAMEHERE with your OS X username so that this corresponds to a folder off your home directory.
Then, in your home directory, make sure that you have a "bin" folder for storing scripts. Create a file therein called join-wifi.sh that contains this:
In this last file, replace the your-network-name-goes-here with the name of the wireless network, and replace your-WPA-key-goes-here with your wireless network's password.
It's not a great solution, and certainly not a secure way to store your wifi access data, but it should work to get you connected at login next time you reboot.