To ensure an intelligent engineering of traffic over satellite networks, the authors have recently proposed a routing protocol dubbed Explicit Load Balancing (ELB). The protocol enables neighboring satellites to explicitly exchange information on their congestion status. A satellite that is about to get congested requests its neighboring satellites to decrease their data forwarding rates. In response, the neighboring satellites search for less congested paths that do not include the satellite in question and communicate a portion of data, primarily destined to the satellite, via the retrieved paths. While transmitting packets of the same flow over different links helps to better distribute the traffic over the satellite constellation, and accordingly alleviates congestion and avoids packet drops, it leads to the reception of packets in an out-of-order manner at the receiver side. In case of TCP, this phenomenon results in the transmission of duplicate acknowledgments, unnecessarily halves the congestion window of TCP, and ultimately degrades the throughput. As a remedy to this issue, we suggest that receivers refer to the Time-to-Live (TTL) field of packet headers to judge whether the out of order in the reception of packets is due to congestion or simply to changes in the communication path. Furthermore, as packets have to traverse more hops in ELB, delay-sensitive applications may get affected by the extra delay due to hops. To cope with such an issue, we consider the use of differentiated services we classify users into a number of classes, namely delay sensitive, throughput-sensitive, and best effort. Via simulations, we demonstrate the efficiency of ELB in such environments.