Great post to check out if you are having network issues with your SBS 2008 network!
We have seen an increase of instances where customers are experiencing various networking problems because they have altered the networking topology by installing multiple NICS or assigning multiple IPs to their single NIC. Some of the more common issues we have seen with this scenario include, but are not limited to:
· Slow or complete loss of file share/network login access
· Problems with Outlook connectivity (mailbox login, Autodiscover, OAB, Free/Busy, OOF assistant, Outlook Anywhere)
· Issues accessing web sites (OWA, RWW, Sharepoint, Connect)
· Issues with service startup, particularly Exchange.
· The server hangs at “Applying Computer Settings” upon boot.
· Inability to complete the SBS networking wizards (IAMW and CTIW)
Received this request earlier today, so getting the word out!
The Windows PowerShell Community Review process is looking for volunteers for our third documentation review cycle – especially beginners and intermediate PowerShell users and people with little or no programming background. Volunteers can contact June at email@example.com or Marco (Marco.Shaw@gmail.com ).
Windows PowerShell Community Review
Have you ever read Help that wasn’t really helpful? Here’s your chance to fix it.
The Windows PowerShell documentation team and PowerShellCommunity.org jointly sponsor the Windows PowerShell Community Doc Review. As a member, you’ll get to read and comment on the Help docs before they’re published, and work with the writers, editors, and the product team to make sure every word is really helpful.
We’re looking for users at all experience levels and with all different backgrounds, but we love to have beginners, people with no programming experience, people who know other scripting languages or shells, and people who are not native English speakers. If you’re a system admin and you don’t really know Windows PowerShell, this is a great way to learn it with help from insiders.
Windows Powershell Spoken Here
OpenDNS is an incredble service, and I highly recommend using it. Word of caution though. If you are sharing an ACT! 2010 database across a peer-to-peer network, the computer names will attempt to resolve to the OpenDNS servers (on the Net) and your other ACT! clients on the network will be unable to attach to the database. A workaround is to use IP addresses, but it’s simpler to remove the OpenDNS server settings and use the default DNS for your upstream ISP.
Otherwise, you’ll be looking at the likes of this:
Error: “The database <Database name> could not be accessed. In order to access this database, check your network connection and verify that your database server is available. It may be necessary to disable any firewall software…
Great tip from the folks at Calyptix:
On DSL connections, if you are experiencing slow Web browsing, or certain Websites and downloads not loading across multiple computers on your network, you might need to change your firewall’s MTU (Maximum Transmission Unit, or largest packet size that can be transmitted) value from the default of 1500 (default on most firewalls) to either 1452 or 1492.
You can check with your ISP for their recommended setting, but a simple way to check is to run a speed test from behind your firewall using each of the three settings (1500, 1492, and 1452) and take the one that reads the highest over a couple tries. For example, with Actiontec DSL modems, Calyptix and SonicWALL firewalls, and Qwest in Seattle, Washington, 1452 is working the best from what I’ve personally seen so far. If you are on Qwest, use http://speedtest.qwest.net/ (always use your ISP’s test if they have one for the best accuracy).