<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0"><channel><title><![CDATA[NetXMS gets the wrong address]]></title><description><![CDATA[<p dir="auto">Client System is Windows 2008 using agent 3.3.314</p>
<p dir="auto">It is a remote system, behind a NAT firewall.  The tunnel connects to the server right away, no problem.</p>
<p dir="auto">But after selecting 'Bind and create node' in the MC, for some reason NetXMS thinks it is on the 192.168.16.0/24 subnet.  But it is on a 192.168.50.0/24 subnet.</p>
<p dir="auto">I have another system there I'm monitoring, and it connected through the tunnel and is being monitored without any problems.</p>
<p dir="auto">The only thing I can think of is that, on our local lan, the same hostname resolves to a 192.168.16.0/24 address.  But NetXMS should not be using our local lan for resolving remote addresses.  Also, I did try manually setting the IP address when in 'Bind and connect' but that didn't work.</p>
<p dir="auto">Because of the wrong IP, after binding, NetXMS can't communicate with the node at all because it has the wrong IP.</p>
<p dir="auto">Help!</p>
<p dir="auto">Thanks,<br />
Ted</p>
]]></description><link>https://forum.netxms.org/topic/6547/netxms-gets-the-wrong-address</link><generator>RSS for Node</generator><lastBuildDate>Fri, 13 Nov 2026 10:11:06 GMT</lastBuildDate><atom:link href="https://forum.netxms.org/topic/6547.rss" rel="self" type="application/rss+xml"/><pubDate>Sat, 23 May 2020 00:44:39 GMT</pubDate><ttl>60</ttl><item><title><![CDATA[Reply to NetXMS gets the wrong address on Sun, 24 May 2020 20:01:47 GMT]]></title><description><![CDATA[<p dir="auto">After restarting the NetXMS server the problem went away.</p>
]]></description><link>https://forum.netxms.org/post/27931</link><guid isPermaLink="true">https://forum.netxms.org/post/27931</guid><dc:creator><![CDATA[tfines]]></dc:creator><pubDate>Sun, 24 May 2020 20:01:47 GMT</pubDate></item></channel></rss>