Month: December 2022

Mitel phone: Coming calls have been transferred to different extension

Situation: The client reports that some coming calls for their group queue have been transferred to different extension 111.

Troubleshooting: We find in their AD profile for a user it looks like 111 is defined as his work phone number. Removing the extension 111 from the user’s Properties fixes the problem.

 

Can’t login his Microsoft 365 with Error Code: 53003

Situation: One of our salespersons can’t login his Office 365 with this error:

 You cannot access this right now

Your sign-in was successful but does not meet the criteria to access this resource. For example, you might be signing in from a browser, app, or location that is restricted by your admin.

Error Code: 53003

Troubleshooting: In most cases, it is related to Microsoft Azure conditional access policy. You can find more information by going to Azure Security page.

  1. After login Azure, go to Security>Conditional Access>Sign-in logs.

2. You can use User contains to fill and find the user who has the issue. That also shows the IP address and location.

3. To see more details, double click on the failed to login username. You can also click on Lunch the Sign-in Diagnostic.

4. Diagnose and solve problems will shows you more details, which will give you more details for troubleshooting. In our example, Conditional access block any access from out of USA.

Please view this step by step video:

Can’t login Cisco switch through SSH

Situation: The client just purchased and configured a new Cisco C9200 switch. They can login Serial without issue. However, they can’t login SSH. SSH doesn’t take the password.

Troubleshooting: Run these configuration commands.

C9200(config)#line vty 0 4
C9200(config-line)#login local
C9200(config-line)#transport input ssh
C9200(config-line)#exit
C9200(config)#ip ssh version 2
C9200(config)#ip ssh authentication-retries 3
C9200(config)#
C9200(config)#ip ssh time-out 120
C9200(config)#exit

Fixing Remote Server returned ‘550 5.1.8 Access denied, bad outbound sender

Situation: One of our clients receives a spam or fishing email. All her emails go to Deleted Item folder automatically. After she changes her Office 365 password, she can’t send email with this return message:

Delivery has failed to these recipients or groups:

helpdesk@chicagotech.net
This message couldn’t be delivered because the sending email address was not recognized as a valid sender. The most common reason for this error is that the email address is, or was, suspected of sending spam. Contact the organization’s email admin for help and give them this error message.

Diagnostic information for administrators:

Generating server: CH2PR16MB3509.namprd16.prod.outlook.com

helpdesk@chicagotech.net
Remote Server returned ‘550 5.1.8 Access denied, bad outbound sender. For more information please go to http://go.microsoft.com/fwlink/?LinkId=875724. S(9333) [PH0PR16MB4914.namprd16.prod.outlook.com]’

Troubleshooting: The virus may create some rules to move all email to the Deleted Item folder and Microsoft 365 may block the email account. scan any virus or malware. If it is clean, reset Outlook rules and unblock the email account.

Step 1: Reset Outlook rules

  1. Login Outlook.
  2. Under Home, click on Rule and select manage Rules & Alerts

3. Delete those rules you don’t create.

Step 2: Unblock the email account

  1. Login Microsoft 365.
  2. Click on Security

3. Click on Review.

4. Delete blocked email address from Restricted entities.