Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Notifications
Login / Register
Community
Community
Notifications
close
  • Forums
  • Knowledge Center
  • Events & Webinars
  • Ideas
  • Blogs
Help
Help
  • Explore Community
  • Get Started
  • Ask the Community
  • How-To & Best Practices
  • Contact Support
Login / Register
Sustainability
Sustainability

Join our "Ask Me About" community webinar on May 20th at 9 AM CET and 5 PM CET to explore cybersecurity and monitoring for Data Center and edge IT. Learn about market trends, cutting-edge technologies, and best practices from industry experts.
Register and secure your Critical IT infrastructure

No Messages Received in AMT from specific I/NET Link or Site

Building Automation Knowledge Base

Schneider Electric Building Automation Knowledge Base is a self-service resource to answer all your questions about EcoStruxure Building suite, Andover Continuum, Satchwell, TAC…

cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Show  only  | Search instead for 
Did you mean: 
  • Home
  • Schneider Electric Community
  • Knowledge Center
  • Building Automation Knowledge Base
  • No Messages Received in AMT from specific I/NET Link or Site
Options
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
Invite a Co-worker
Send a co-worker an invite to the portal.Just enter their email address and we'll connect them to register. After joining, they will belong to the same company.
You have entered an invalid email address. Please re-enter the email address.
This co-worker has already been invited to the Exchange portal. Please invite another co-worker.
Please enter email address
Send Invite Cancel
Invitation Sent
Your invitation was sent.Thanks for sharing Exchange with your co-worker.
Send New Invite Close

Related Forums

  • Intelligent Devices Forum

Previous Next
Contributors
  • DavidFisher
    DavidFisher
  • CraigEl
    CraigEl
  • Derrick_Ratliff
    Derrick_Ratliff
  • Product_Support
    Product_Support

Invite a Colleague

Found this content useful? Share it with a Colleague!

Invite a Colleague Invite
Back to Building Automation Knowledge Base
Options
  • Bookmark
  • Subscribe
  • Email to a Friend
  • Printer Friendly Page
  • Report Inappropriate Content
0 Likes
1455 Views

Link copied. Please paste this link to share this article on your social media post.

Trying to translate this page to your language?
Select your language from the translate dropdown in the upper right. arrow
Translate to: English
  • (Français) French
  • (Deutsche) German
  • (Italiano) Italian
  • (Português) Portuguese
  • (Русский) Russian
  • (Español) Spanish

No Messages Received in AMT from specific I/NET Link or Site

Picard Product_Support
‎2018-09-11 06:57 AM

Last Updated: Administrator CraigEl Administrator ‎2022-08-09 09:32 PM

Issue

No Messages Received in AMT from specific Link or Site

Product Line

TAC INET

Environment

  • I/NET Seven
  • Xenta 527-NPR
  • Xenta 527 Web Server
  • NPR2000

Cause

There are many causes outlined in AMT not receiving Data which show reason why AMT may not be receiving data. In some cases the issues is not due to programmatic issues but network Errors.

I/NET uses UDP port 50069 to broadcast data from NPRs and Xenta 527s to any listening host device. While this does give the flexibility to have multiple hosts receive the same packet, it prevents the proof of delivery that a TCP packet provides.

You can read more about UDP at this link.

http://en.wikipedia.org/wiki/User_Datagram_Protocol

Resolution

 To prove a network error, use the following methods:

  • Verify everything listed in AMT not receiving Data
  • If feasible, repeat those steps above direct connected to the Xenta 527 via crossover cable. Ensure Window Firewall is disabled on the local PC when performing this task.
  • Once you have a PC that will receive Messages while direct connected, re-connect the 527 to the network and use the same PC to connect to try to 527 over the network. If AMT works or fails based on being on or off of the network, then this is a networking issue.

The PC, Domain Server, or Internet Service provider are all capable of blocking I/NET communication. This can be done by either blocking traffic going out of the PC(s) to the NPR/527(s), or it can block traffic from the NPR/527(s) to the PC. On a PC Windows Firewall these are referred to as outbound rule and inbound rule respectively.

Please note the following conditions when certain parts of the network traffic are blocked.

Traffic Blocked on traffic from NPR to PC Traffic Blocked on Traffic from PC to NPR Both Blocked
You can connect to controllers in I/NET, values will update and you can control points You cannot connect to controllers in I/NET, values will not update and you cannot control points You cannot connect to controllers in I/NET, values will not update and you cannot control points
AMT does not receive data from the blocked Link or Site AMT does not receive data AMT does not receive data

 

To Correct a PC Windows Firewall Issue:

  1. You will be able to prove a windows firewall issue by turning off the PC firewall for a few minutes and testing AMT. If traffic resumes, this is the cause.
  2. Open Windows Control Panel
  3. If needed, change "View By" from Category to Small Icons
  4. Click on Windows Firewall
  5. Select Advanced Settings
  6. Click on Inbound Rules
  7. Click on New Rule in the Actions Pane
  8. Select Program and click Next
  9. Browse to the InetIoSrv.exe application on your PC. Click Next
  10. Select the Action to Allow the connection and click Next
     
  11. Set the Rule to apply to all locations. Click Next
  12. Name the Program and Click Finish.
  13. AMT Should begin to receive data. If not, repeat step 1 to verify this is a PC firewall issue and contact Product Support for additional assistance.

If the data is being blocked by the network and not the PC Firewall:

  1. Contact your network administrator and explain that the Xenta 527 or NPR 2000 must be able to broadcast UDP data on UDP port 50069. This path must be open on every hop between the device and the PC.
  2. Verify that both the PC and device are on the same Windows Domain. Typically, UDP traffic will not travel outside of the Domain.
  3. If you are unable to get network blocked removed, you may be forced to put all I/NET devices and PC's on a single subnet.
Labels (1)
Labels:
  • TAC INET
Tags (1)
  • Find more articles tagged with:
  • 15627
Was this article helpful? Yes No
No ratings

Link copied. Please paste this link to share this article on your social media post.

To The Top!

Forums

  • APC UPS Data Center Backup Solutions
  • EcoStruxure IT
  • EcoStruxure Geo SCADA Expert
  • Metering & Power Quality
  • Schneider Electric Wiser

Knowledge Center

Events & webinars

Ideas

Blogs

Get Started

  • Ask the Community
  • Community Guidelines
  • Community User Guide
  • How-To & Best Practice
  • Experts Leaderboard
  • Contact Support
Brand-Logo
Subscribing is a smart move!
You can subscribe to this board after you log in or create your free account.
Forum-Icon

Create your free account or log in to subscribe to the board - and gain access to more than 10,000+ support articles along with insights from experts and peers.

Register today for FREE

Register Now

Already have an account? Login

Terms & Conditions Privacy Notice Change your Cookie Settings © 2025 Schneider Electric

This is a heading

With achievable small steps, users progress and continually feel satisfaction in task accomplishment.

Usetiful Onboarding Checklist remembers the progress of every user, allowing them to take bite-sized journeys and continue where they left.

of