Why does my Serial affect my Ethernet?

Can someone tell my how the Serial Port A could possibly affect the Ethernet connection?

Here’s a play by play for the code in question:

DHCP for 5 seconds - it fails to default IP
Ping to remote IP - I see the request/reply on packet sniffer
Start serial port A - lose connection to stdio on DynC IDE
Ping to remote IP - I see the request/reply on packet sniffer
Send information via UDP packet to Rabbit - data contains a serial string to transmit
Ethernet port loses comms - no more packets are received from the ethernet port (this is a poll/response situation)

I have code if needed, but that can be handled on an email basis.

Jim Sunshine.

Don’t know about the rest, but I believe the debugger cable uses port A. If you use port A while debugging, your debugger will disconnect. We use a macro to conditionally compile our code. We turn off port A for debugging, then on when compiling to bin image.