F
Frank
On a XP machine we are using the MS loopback adapter for
test purposes when the computer is not connected to a
network. The loopback adapter creates abnormal program
termination when a lot of tcp/ip-traffic is exchanged
between two programs. The same programs works fine when we
use a network or if the traffic between the programs is
exchanges slowly. It also runs when we use the loopback
adapter on a Win 2000 machine.
My question are:
- Is there a way to solve this?
- Is this a known bug of the MS loopback adapter in XP?
- I wanted to test the traffic with a sniffer, but it
seems to be impossible to sniff traffic through the
software adapter. Does anybody know a tool for that.
- Could it be other problems than the adpater? If yes,
what could be possible reasons?
Thanks a lot for your help,
-- Frank
test purposes when the computer is not connected to a
network. The loopback adapter creates abnormal program
termination when a lot of tcp/ip-traffic is exchanged
between two programs. The same programs works fine when we
use a network or if the traffic between the programs is
exchanges slowly. It also runs when we use the loopback
adapter on a Win 2000 machine.
My question are:
- Is there a way to solve this?
- Is this a known bug of the MS loopback adapter in XP?
- I wanted to test the traffic with a sniffer, but it
seems to be impossible to sniff traffic through the
software adapter. Does anybody know a tool for that.
- Could it be other problems than the adpater? If yes,
what could be possible reasons?
Thanks a lot for your help,
-- Frank