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

We Value Your Feedback!
Could you please spare a few minutes to share your thoughts on Cloud Connected vs On-Premise Services. Your feedback can help us shape the future of services.
Learn more about the survey or Click here to Launch the survey
Schneider Electric Services Innovation Team!

IP Packages are sent out on the wrong network interface.

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
  • IP Packages are sent out on the wrong network interface.
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
  • MathiasBj
    MathiasBj
  • DavidFisher
    DavidFisher
  • Sacco
    Sacco
  • 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
1031 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

IP Packages are sent out on the wrong network interface.

Picard Product_Support
‎2018-09-06 02:59 PM

Issue

IP Packages are sent out on the wrong network interface.

Environment

PC configured to use more than one network interface (Multihomed)

Cause

When a PC should send out a TCP/IP network package to another device it will determine if the destination device is located on the same local network. If it is, the PC can address the message directly to the device's IP address. If it is not, the package need to be sent to a router that can route the message to its final destination using what is called a default gateway. This is normally no problem when the PC is connected to only one network but if it is connected to more than one network that uses gateways to route the traffic on the networks, the PC does not always know which network interface to use for messages that are not addressed to one of the local networks.

Resolution

Tell the PC which routing path to use for a destination address or a destination network. If your PC is configured to use more than one network interface (Multihomed) and your packages are not sent out on the correct network interface, you need to add a routing path for this or those destinations using the "Route ADD" command in Windows via the command prompt.

Example: Add a route path for a network: route add 192.168.2.0 MASK 255.255.255.0 192.168.0.1 ^ 1 ^ 2 ^3
1 = Network address where the devices are located
2 = Network Subnet mask
3 = IP address of the router (gateway) that should be used to forward the packages.

Add a route path per device: route add 192.168.2.25 MASK 255.255.255.255 192.168.0.1 route add 192.168.2.26 MASK 255.255.255.255 192.168.0.1 ^ 1 ^ 2 ^3
1 = IP address of the destination device.
2 = should always be 255.255.255.255
3 = IP address of the router (gateway) that should be used to forward the packages.

For more information of how to use this command, type "route help add" in the command prompt.
Note that added route paths are not persistent by default and will be erased after a system reboot. To make them persistent you need to add the command -p route -p add 192.168........

Labels (1)
Labels:
  • TAC Vista
Tags (1)
  • Find more articles tagged with:
  • 2553
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