Tuesday, 17 May 2016

New DC Unable to Get rID Set

I recently added another domain controller (DC) to my SBS2011 R2 network. I checked it out at the command line with >DCDiag /dnsall and found it wasn't working. Further tests with >DCDIAG /dnsall showed me that my new DC didn't receive an rID Set from the rID Master.

Running >repadmin /options <Main DC Name> showed that both inbound and outbound replications were switched off, I switched them back on and my new DC received an rID Set almost immediately.

To reset INBOUND/OUTBOUND DC replications and ensure that they are switched on run the following commands:
>repadmin /options +DISABLE_INBOUND_REPL <Main DC Name>
>repadmin /options -DISABLE_INBOUND_REPL <Main DC Name>
>repadmin /options +DISABLE_OUTBOUND_REPL <Main DC Name>
>repadmin /options -DISABLE_OUTBOUND_REPL <Main DC Name>

Useful commands for domain controller testing:
>NSLookup /?
>DCDiag /?
>repadmin /?

You can have as many DCs as you need on an SBS network as long as the FSMO rID Master role remains on the SBS server.

Thursday, 5 May 2016

ERROR Connecting to a Shared Printer

I kept getting an error when I tried to connect to a shared printer. The solution i found is to add the shared printer as a local printer and set the port to the network share.

1. Control Panel/Devices and Printers/Add a Printer
2. Select 'The printer I want isn't listed'
3. Select 'Add a local printer or network printer with manual settings'
4. Select 'Creat a New Port' / Local Port
5. Enter the network share as the port name \\<Network Computer Name>\<Printer Share Name> or \\<IP Address>\<Printer Share Name>
6. Select your printer from the list of available printers

If your printer is not listed the best solution is to download and install the drivers from the printer manufacturers support website. You can, however, try a generic driver.

Wednesday, 4 May 2016

Office 365 Error Code: 30143-37

What fixed it for me was to delete the sub-directory "C:\Program Files\Microsoft Office 15" and then restart the installation.

Saturday, 17 January 2015

Exchange 2013 Returning Messages and Attachments over 5MB

I  was unable to receive any messages over 5MB. I had checked all the usual settings, ISP, Receive Connectors, Send Connectors, Transport Rule Limits, and Mailbox Limits and confirmed that they were set to 100MB, both from EAC and also from the Management Shell. I also ran >telnet <exchange server> 25 followed by EHLO and confirmed '250-size 104857600. All email larger than 5MB was returned with the following two messages:
1. Your message is too large to send. To send it, make the message smaller, for example, by removing attachments.
2. Remote Server returned '< #5.2.3 smtp;550 5.2.3 RESOLVER.RST.SendSizeLimit.Org; message too large for this organization>'

The fix for me was to run the following command in the Exchange Management Shell:

>Set-TransportConfig -ExternalDsnMaxMessageAttachSize 100MB -InternalDsnMaxMessageAttachSize 100MB -MaxReceiveSize 100MB -MaxSendSize 100MB

Use Get-TransportConfig to verify your settings.

Wednesday, 7 December 2011

Implementing Account Lockout Policy SBS 2011

To implement/edit account lockout policy in Small Business Server do the following.

1. Start/Administrative Tools/Group Policy Management

2. Forest/Domains/<Your Domain>


3. Right-Click “Windows SBS User Policy” /Select “Edit”


4. Computer Configuration/Policies/Windows Settings/Security Settings/Account Policies/Account Lockout Policy


5. Double-Click the items in the right hand pane to enable and set the Account Lockout Parameters.

Sunday, 23 October 2011

Inbound Ping through the Firewall WS2K8R2 / W7

Start / Control Panel / Windows Firewall / Advanced Settings / Inbound Rules
New Rule / Custom / Protocols and Ports / Protocol type / ICMPv4
Customize / Specific ICMP types / Echo Request / OK
Keep pressing Next until you are asked for a rule name
Type a name for the rule. Press finish.

Tuesday, 18 October 2011