Technical Archives – Page 9 of 12

How to manually connect Outlook to Office 365 Hosted Exchange

Posted on December 13, 2013March 12, 2023 by Mark Pace

Hooking Outlook to Office 365 or Hosted Exchange is a little different to a local server.

In this article we will explain step by step, how to manually connect Microsoft Outlook to Office 365.

Part 1

Before we begin we need to gather a bit of information.

3. Under Microsoft Office Outlook Connectivity Tests click on Outlook Autodiscover.
4. Fill in the information: Email address and Microsoft Account are your Office 365 Username.
5. Password, is your Office 365 password.
6. Check “I understand the terms and conditions…” and continue.
7. When the test is done hit Expand All.
8. On your keyboard press Ctrl+F and type “Server” within the Find tool. Copy this information within “<Server>” and “</Server>” as you will need it later.

Note: It is highly recommended that you change your Office 365 password after using the above website.
Note: If you are doing this for multiple Users, please be reminded that their mailbox may not be within the same Server as your other Users. It is recommended that you use this tool each time you wish to find your Users Server.

Part 2

Now on your computer.

1. Next click on Start.
2. Click on Control Panel.
3. Navigate over to Mail.
4. Select Show Profiles.
5. And click New.
6. Enter a new Profile Name.
7. Within Add Account : Select Manual Setup of Addition Server Types.
8. Select Microsoft Exchange Server Or Compatible Service.
9. Within “Server:” Paste your Server Name from Part 1. Step 8.
10. Within “UserName:” type your Office 365 Account Username (User@mydomain.com).

11. Click More Settings.
12. Under the Security Tab, uncheck “Encrypt Data between Microsoft Outlook and Microsoft Exchange“.
13. From the “Logon Network Security” drop down box select Anonymous Authentication.
14. Click on the Connections Tab.
15. Check Connect to Microsoft Exchange Using HTTP.
16. Click on Exchange Proxy Settings….
17. On the right of “Https://” type outlook.office365.com
18. Check “Only connect to proxy servers that have this principal name in their certificate:” and type msstd:outlook.com
19. Check “On Fast Networks, connect using HTTP first, then connect using TCP/IP”
20. Under Proxy Authentication click the drop down box and select Basic Authentication.

21. Hit Okay twice and continue with your setup.

How to Block Porn on iOS 7 for iPhone, iPad & iPod Touch – Adult Filter

Posted on October 19, 2013 by Mark Pace

Business’, Parents and users looking to block porn on the iPhone and iPad should be first in line to update to iOS 7.

Apple includes enhanced parental controls on iOS 7 including an iPad and iPhone porn block feature that can restrict the ability of users to access websites with adult material.

Like any internet filter, this iPhone porn block feature isn’t going to be perfect, but in our tests the iOS 7 porn filter did a good job of preventing access to questionable websites.

This is a free feature in iOS 7 and it is at the system level so it can block porn and other adult themed websites throughout the device without requiring the user to use a specific browser.

The iPhone porn block feature is new in iOS 7.

In our testing, the iPhone porn block mode even carries over to Google Chrome on the iPhone, so kids and users can’t just download a new browser to get around this.

First off you will need to update to iOS 7 to use the Adult Web Filtering feature. This is a new feature in iOS 7, and it is a free update.

When you have iOS 7 installed the following steps will get you to the point where you can block adult material on the iPhone and iPad.

Settings -> General -> Enable Restrictions -> Websites -> Limit Adult Content

This will prompt you to enter a pass code, and you should make it one that is different from the user’s unlock code, or they can turn it on and off at will. When prompted create a secret code that the user will not know.

Parental controls in iOS 7 let users block porn on the iPhone, iPad and iPod touch.

To turn off the iPhone porn blocking feature in iOS 7, enter the pass code and turn restrictions off. If the pass code is locked you may need to reset the iPhone, iPad or iPod touch.

Because no Internet filter is perfect, the parent or administrator can manually block and allow certain websites always. Enter these in the settings menu, or enter the pass code when browsing to add an attempted address to the list.

Thank you: Source
Read more at https://www.gottabemobile.com

CRITICAL WARNING VIRUS ALERT – CryptoLocker – Prevention and Clean

Posted on October 15, 2013 by Mark Pace

Please read and take note
CryptoLocker 14th October 2013

CryptoLocker is the next generation of internet virus that is currently circulating all over the world in large numbers. Once a computer becomes infected it will lock all your files plus any network files it has access to, even your server.
Once the files are locked it will give you a three day countdown to pay the ransom, usually $100 or $300. If the time expires your files are locked with no option to pay the ransom.
It is by far the worst we have experienced so far and virus protection companies are scrambling to catch up with this one, as it changes frequently to elude the virus scanners. In other words: it can affect you if you are not careful even though your firewall and virus protection is active and up-to-date.
Currently there are only two known methods to remove the infection, restoring your files from a backup or paying the ransom.
Please be aware that paying the ransom is not guaranteed to work. We don’t condone paying the ransom and supporting these cybercriminals.

Usually this occurs by these methods:
In the form of attachment, usually disguised in an email appearing to come from your bank, insurance company or courier service or scanner.
A simple safety procedure that works for the majority of email applications or online email services is to “hover” over the link, which means move the cursor to the attachment or “button” or other link in the email, but DO NOT click. If the domain name that appears has no relation, looks suspicious, or appears as an unintelligible tangle of letters and numbers, it usually means it is not legitimate and should be deleted.
Through Trojan websites, which will ask you to download a piece of software in order to watch video clips or download songs off the internet.
Through exploit kits, specific websites with similar names to popular ones, just waiting for people to miss-type the address and think they are on their favourite website.
Advice for prevention

Do not open attachments if you are unsure of the contents or the email was unexpected.
Look for clues in the email content, usually most legitimate emails will address you by name and not something generic like ‘customer’ with vague wording.
Do not click on website links in emails until you have viewed the link location (do this by hovering over the link, this will display the link right at the bottom of Outlook). Instead of clicking the link, you are best to manually browse to the website via your web browser.
Make sure your anti-virus is updated regularly
Make sure your backups are current and working and backing up ALL critical data
If you get the virus

Stop work
Immediately disconnect any network drives
Contact us
Alert other users of the issue, as most likely any work done will be overwritten when the backup is restored.
Please do forward this email on to your staff, friends and associates.

If in doubt or have any questions, please contact Sterling IT.

Forward or redirect problem on exchange 2007/2010 not working

Posted on September 23, 2013 by Mark Pace

When trying to do a redirect on a mailbox externally, it was not processing the email.
Internal was fine.

Apparently forwarding / redirects to external domain names is disabled by default in Exchange 2007 and 2010.

To change this setting, open the Exchange Management Console, and drill down to the Organization Configuration -> Hub Transport. Under the Remote Domains tab, open the Default domain.

Then, on the format tab, check the “Allow automatic forward” box.

Alternatively, from the Exchange Management Shell (PowerShell rocks!), this will do the trick:

set-remotedomain -identity Default -AutoForwardEnabled $true

How to Enable Forwarding Emails to Other Email Addresses in Microsoft Office 365

Posted on August 30, 2013 by Mark Pace

If you don’t want to connect your others account in Microsoft Office 365 but there is another feature present in Microsoft Office 365 which allows you to receive emails without connecting them in Office365.
Forwarding email is that feature which will help you to receive you emails (which have sent on your Office 365 email address).

1- Log into your Microsoft Office 365 account.

2- After signing in, select Options which is present under Outlook Category.

3- After selecting, Options section will be open in new tab window and now select Account from the left sidebar.

4- Now open the Connected Accounts tab which is present on the right side.

5- After opening the tab, enter the email address to which you want to forward your emails and click on the ‘Start Forwarding’.

6- Now click on ‘Save’ to save all the settings which have done.

After following all of the above mentioned steps you can easily enable forwarding emails to other email addresses in Microsoft Office 365.

What is DNS and Records?

Posted on August 6, 2013 by Mark Pace

Found some really good information on DNS and rather than reinvent the wheel, I thought I would share this with you.
Credits at the bottom of the article.

DNS (Domain Name System) is a simple service many in IT don’t understand. It’s essentially the phone book for any network — especially the Internet. When you surf the web you use DNS. If not, you would have to remember every system’s IP address you wanted to visit. Instead of Google.com or Amazon.com, you would have to remember 74.125.239.82 and 205.251.242.54 and every backup IP address they use for load balancing the traffic.

There are many different providers of DNS. They’re your ISP (home or business), Google, Level 3, OpenDNS, DynDNS, etc. Your home ISP will often provide features like search assist or phishing block to help protect you while you’re searching the web. Google (8.8.8.8 and 8.8.4.4) and Level 3 (4.2.2.1 and 4.2.2.2) provide DNS servers that don’t block any requests (unfiltered) so you don’t have to use your ISP’s DNS services if you don’t want to.

OpenDNS and DynDNS offer services — for pay and for free — that allow you to control what kind of sites you wish to block and what sites you wish to allow. Pay accounts often give you more control down to individual sites rather than categories of sites. This is a popular method for securing home Internet service to protect kids from looking at content you don’t want them to look at — without having to hover over them as they browse the Internet. It’s also good for protecting you from phishing scams.

A records
Basic DNS records are called A records. These are Address Records for a hostname. For example, if you look at the A records for www.google.com you will find several entries that include 74.125.227.209, 74.125.227.210, 74.125.227.211, 74.125.227.212, and 74.125.227.208 as well as one that looks different than the others: 2607:f8b0:4000:803::1013. This one is IPv6 where the others are IPv4. Having multiple records like this doesn’t give true load balancing. If you surf to www.google.com and DNS tells your system that it needs to contact 74.125.227.209 and it doesn’t respond, your system doesn’t ask again — it gets 74.125.227.210 and continues. It will ask the question once and if it gets an answer (even one that states the address can’t be resolved) your browser will attempt to connect to it and return the web page or a “page doesn’t exist” error page.

MX records
DNS records are also used to route email around the Internet. These are called MX records. They usually point to a group of computers that are responsible for receiving mail for the organization. Each entry will have a priority associated with it — this provides a failover so if one mail server isn’t responding, the sending mail server can try the next one in the list.

NS records
So what are DNS servers called in DNS records? NS, or Name Servers, are the servers that are responsible or have authority for the domain zones they host. This also helps with replicating the changes in the DNS zone between servers that are responsible for each DNS zone.

PTR records and rDNS
There are also reverse records called pointer (PTR) records. These help with security. If a system receives email, it knows what IP address it came from. It will do a reverse DNS (rDNS) lookup to see what domain name it came from. Then it compares this with the MX records to see if this server is registered as an email server. If not, it can reject the email as spam.

Another use is in network troubleshooting when you know the IP address but don’t know the system name. PING and TRACERT (trace route) commands will show you the IP address and the DNS name.

CNAME records
Another popular record type is a CNAME. This is a Canonical NAME record — think of it as an alias record. It is used when one IP address is used for multiple services. For example, let’s say you have a website named www.yourwebsite.com and it has an IP address of 10.1.2.3, but you also have other services you wish to publish, like FTP.

Rather than making another A Record for ftp.yourwebsite.com, you can make a CNAME for ftp.yourwebsite.com and point it (alias) to www.yourwebsite.com. When/if you change the IP address for your website (change of providers), then you only have to update one record (the A Record) for www.yourwebsite.com and all of your CNAME records will automatically be redirected to the proper IP address.

However, there are some rules that should be followed with CNAME records.

You should never point a MX record to a CNAME.
You should never point a NS record to a CNAME.
You shouldn’t point a CNAME to a CNAME as it could create a never-ending loop.

SRV records
Corporate DNS used for Active Directory Domains takes this further and includes records that help computer systems authenticate on the network and determine what domain controller is closer, what file server is closer, what the email server auto-setup should be, etc. These records include SRV records that are used for Kerberos, LDAP, and other services as the domain needs to function.

So what system holds the DNS for corporate servers (Active Directory)? Active Directory servers run DNS service that clients — other computers on the internal network — will point to them for all DNS needs. It’s up to the internal DNS servers to decide if the request is for an internal (private) record or for a public record.

If it needs a public record, there are several ways a DNS server can find the information. It can point to a set of servers either for all domains or for just a specific domain. It can use root hints to direct traffic to the proper public DNS servers. Or, it can also use a combination of the two — depending on the needs of the organization.

If you have an Active Directory environment and you point your client (or the DNS client on a domain controller/DNS server) to a public DNS server, your domain won’t function properly. The public DNS servers won’t have the records for your private DNS zone and won’t have any way to get them if your client requests it. This will prevent your computer from authenticating on the domain, joining the domain, connecting to your email server, surfing your corporate intranet, etc.

Split DNS
Let’s say you’re in a corporate environment. You have a web server that you list as www.yourwebsite.com with a public DNS record of 74.125.227.210 (this is Google’s IP address — I’m only using this as an example). But, you’re inside your network and your firewall won’t allow traffic to go out, make a u-turn and come back in so you can’t get to the website. How do you resolve this for your internal clients? You make a split DNS.

This means there is a public DNS zone for yourwebsite.com that contains an A Record for www. that resolves to 74.125.227.210 and you have an internal DNS zone (on your domain controller or domain DNS server) that also has a zone for yourwebsite.com but has an A Record for www. that resolves to 10.1.2.3 (the internal IP address for the same web server).

Now your client on the inside of your corporate network can communicate with your web server at www.yourwebsite.com. If this is a mobile device, you could move between networks (corporate, public Wi-Fi, home) and still have access to the website. Of course, with this split DNS zone, you’ll have to enter every record that’s in the public DNS zone or you will break the other records while on the internal network.

Another split DNS zone implementation is to do it just for the record you wish to redirect. You would create a DNS zone for www.yourwebsite.com and have the default record resolve to 10.1.2.3 — this way you only have to maintain one record internally instead of every record that is in the public DNS zone.

da Beast Aug 6, 2013 at 4:42 AM | DNS
This is the 223rd article in the Spotlight on IT series.
Source: https://community.spiceworks.com/topic/366432-the-name-game-from-dns-ignorance-to-enlightenment?utm_campaign=0805&utm_medium=+spotlight&utm_source=+swemail