This is what solved my problems with WiFi disconnecting randomly, not appearing after awakening, etc.
1. Open network preferences from your WiFi icon in the menu bar. Then click advanced. Delete the network that is giving you problems.
2. Open Keychain in the utilities folder of your hard drive. Find the passwords that are stored for your particular network and delete them. There may be multiple passwords for your network, so search carefully.
3. Repair permissions using the disk utility.
4. Reboot the computer.
5. Reenter your network data to log into the network.
Cool slide show on Virtual Networking
A great little Slide Rocket on understanding the basics of virtualized networking by Joe Keegan.
http://portal.sliderocket.com/CPWRJ/C8FA6E8D-2795-42F8-AA68-D4AB081DC810
Procedure to mount remote windows partition (NAS share)
1) Make sure you have following information: ==> Windows username and password to access share name ==> Sharename (such as //server/share) or IP address ==> root level access on Linux
2) Login to Linux as a root user (or use su command)
3) Create the required mount point: # mkdir -p /mnt/ntserver
4) Use the mount command as follows: # mount -t cifs //ntserver/download -o username=vivek,password=myPassword /mnt/ntserver
Use following command if you are using Old version such as RHEL <=4 or Debian <= 3: # mount -t smbfs -o username=vivek,password=D1W4x9sw //ntserver/download /mnt/ntserver
5) Access Windows 2003/2000/NT share using cd and ls command: # cd /mnt/ntserver; ls -l
Where,
- -t smbfs : File system type to be mount (outdated, use cifs)
- -t cifs : File system type to be mount
- -o : are options passed to mount command, in this example I had passed two options. First argument is password (vivek) and second argument is password to connect remote windows box
- //ntserver/download : Windows 2000/NT share name
- /mnt/ntserver Linux mount point (to access share after mounting)
How to configure PathSolutions for use with a proxy server
Details: When a proxy server is used instead of a firewall, the license mechanism may not be able to connect to the PathSolutions license server on the Internet to validate its configuration. Thus, the program may fail to connect when it initially tries to validate its license, or may fail in the future if the proxy server is not properly configured.
Deployment: Microsoft has included a different proxy server configuration tool for different versions of its operating system. Use the below procedure associated with your OS version.
Microsoft Windows NT/2000/2003/XP (32bit)
Internet Explorer should be configured with the correct proxy server settings. Once that is completed, validate that it is working by browsing to the following test page:
https://sub01.nlsubscription.com/test.htm
If the test page works, the same proxy server configuration can be utilized by PathSolutions to validate its license. Enter the following command to configure Windows to use the same proxy configuration as IE:
proxycfg –u
At this point, you should be able to validate your license against the license server using SSL.
Microsoft Windows Vista/2008/7 (32bit)
Internet Explorer should be configured with the correct proxy server settings. Once that is completed, validate that it is working by browsing to the following test page:
https://sub01.nlsubscription.com/test.htm
If the test page works, the same proxy server configuration can be utilized by PathSolutions to validate its license. Enter the following command to configure Windows to use the same proxy configuration as IE:
NetSH WinHTTP import proxy source=ie
At this point, you should be able to validate your license against the license server using SSL.
Microsoft Windows Vista/2008/7 (64bit)
Internet Explorer should be configured with the correct proxy server settings. Once that is completed, validate that it is working by browsing to the following test page:
https://sub01.nlsubscription.com/test.htm
If the test page works, the same proxy server configuration can be utilized by PathSolutions to validate its license. A special 32bit version of the NetSH program must be run to do the configuration.
Use the following procedure:
1) Open a CMD window
2) Change directory to C:\Windows\SysWOW64
3) Enter:
NetSH WinHTTP import proxy source=ie
At this point, you should be able to validate your license against the license server using SSL.
How to track down duplicate MAC addresses out of the ARP table dump?
Use this easy parsing command using uniq to pull duplicates out of the arp table dump that you can grab from your routers.
cat arp_dump_XXXXXXXXX.txt | awk ‘{print $1″ “$3}’ | uniq -D -w 17
That gives you the duplicates from row 1 and the read out of row 3 which is the IP address and Name.