Sep 13 2006
KB: Technical Analysis of the 9/13 MedNet Connection Problem
Problem Users from within the Medical Enterprise network are unable to connect to the 164.67.228 network.
Becuase ISIS resides on this network, MedNet users are unable to connect to ISIS.
Background and Analysis
Because of the private IP address network at MedNet, Mednet and AIS has a direct private link between the two networks to facilitate resource access. There is one firewall at each end of this direct link. AIS manages the AIS side, MCCS manages the MedNet side.
AIS began receiving reports of connection problems at around 8AM on 9/13/06. However, according to the ISIS log, we stopped receiving traffic from the MedNet private 10.n.n.n network at around 10:23pm on 9/12/06.
The AIS firewall log is not recording connection attempt from the 10.n.n.n network to the 164.67.228 subnet. However, we are seeing valid connection attempts from 10.n.n.n addresses to other AIS subnet.
The only exception: there was a brief burst of 8 connections to 164.67.228.231 from 10.254.1.10 at 12:42pm on 9/13.
Both AIS and MCCS staff have confirmed that the firewalls are not blocking relevant traffic in either direction.
