Thread Info
  • State Verified Answer
  • Locked Locked
  • Replies 8 replies
  • Subscribers 1 subscriber
  • Views 14599 views
  • Users 0 members are here
Options
Suggested
This discussion has been locked.
You can no longer post new replies to this discussion. If you have a question you can start a new discussion

Unexplained Network Traffic to Parent Router

agvonline

Hi

I have a 2012R2 Server with Sophos Enterprise Console 5.2.1R2 installed.

The server has two NICs, one on the 'default VLAN' and one on a 'SAN VLAN'.

On the server...

I have removed the 'SAN VLAN' IP address/interface from the MRINIT.CONF file.

In the registry I have also modified the -ORBListenEndpoints for the RMS and Server Agent so that only the 'default VLAN' IP address is used.

On the client(s), In the Remote Management logs I can see the IOR being received from the server, and using an online checker I have been able to see that the IOR contains only the 'default VLAN' address (<default VLAN IP Address:8193>

So all looks ok.

But, our network is being flooded with TCP traffic from all the clients trying to send data to the 'SAN VLAN' on port 8194.

How can this be? The IOR doesn't include that address, so how could the clients possibly know about it? On the clients I can't find any reference to the 'SAN VLAN' address in the registry and the MRINIT.CONF file is correct.

I'm really confused. Please help.

Thanks

Andrew

:46501


This thread was automatically locked due to age.
Parents
  • 0

    Thanks for the reply.

    Please don't be confused :-) I didn't want to over complicate the initial post.

    I found out via our firewall, which is logging blocked traffic. The many entries look like the following:

    Source: 172.21.4.182, port 49842  -- Destination: 10.113.0.4, port 8194

    The 'Destination' being the IP address of the NIC card the server uses to access a SAN.

    The 'Source' is a client on the Default VLAN.

    No connection to 10.113.0.4 is possible from the client. What doesn't make sense is how the clients even know about this interface.

    :46505
Reply
  • 0

    Thanks for the reply.

    Please don't be confused :-) I didn't want to over complicate the initial post.

    I found out via our firewall, which is logging blocked traffic. The many entries look like the following:

    Source: 172.21.4.182, port 49842  -- Destination: 10.113.0.4, port 8194

    The 'Destination' being the IP address of the NIC card the server uses to access a SAN.

    The 'Source' is a client on the Default VLAN.

    No connection to 10.113.0.4 is possible from the client. What doesn't make sense is how the clients even know about this interface.

    :46505
Children
No Data