private server dropouts and buffering

[para7rha]

sorry if I have posted this in the wrong place but I have a problem but cant seem to solve!

I'm using winamp with the shoutcast dsp plugin to send a stream privateley to the server for a radio station for live broadcast relay. It does not matter what kbs I broadcast in the station drawing the stream is reporting drop outs and buffering.
I have scanned my pc for viruses and spyware using various programs and know it is clean and all other programs apart from winamp and shoutcast GUI server are closed and firewall is configured to both programs.

I have a 2mb up/down connection and during the stream it is using very little of the bandwidth and I'm not as far as I'm aware bursting packets.

the winamp is the latest version but I have now d/led version 2.9 to try...
the codec is Nullsoft SHOUTcast DSP 1.8.2

my pc is pentium4 3.2
2 gig of ram
using acatel modem

I'm convinced the problem is not my end can anyone advise if it could be a program codec issue..
I have run a test in 128kbs mp3 using sam3 and the listener nether had any buffering

Thanks

[Edit --> DJ Egg]
Moved from Winamp Tech to SHOUTcast Tech Support.

[djSpinnerCee]

You have way too much hardware!

Just kidding -- :) Things to check:

Today a fellah was using too many plug-ins in WinAMP - more specifically, a crossfade plugin (under a DSP stacker maybe?) that was taking too long to do it's stuff... Check the CPU util on the source box.

The connection from the source/DSP to the DNAS -- local I assume? same PC maybe? -- if it's the same PC, use 127.0.0.1 in the DSP address... If the DNAS is on the same LAN, use the DNAS LAN IP -- Avoid the temptation to use the public WAN IP -- it allows the router NAT logic to get in your way -- The public IP works (with some routers), but is the worst of the "choices" you can make.

Verify your upload rate -- the ISP rating is not important, it's what you really get right now that means anything -- http://nyc.speakeasy.net/ -- try all sites -- use the worst one to determine what you really have available to you.

You also need to verify what is going on at the remote relay site -- while you may have all your ducks in a row, they may not. Proxies and other network noise may be in their way. Pings and tracerts are good tools when run on both ends.

The station is reporting drop outs ? Their listeners? The relay should visit your DNAS as a listener -- what do YOU see for the DNAS in your stats -- if the relay is underrunning the "feed" from your DNAS, you'll certainly see it in your /admin.cgi plain as day. Also pay attention to the buffer position -- a few K is fine, close to a Meg or two indicates a communication issue (and impending underrun) between you and the relay.

[para7rha]

Thanks for your reply! checked the things you have mentioned.....could it be the port i'm streaming through :8000