I've had this same problem pretty consistently since 0.4.8.  Just upgraded to 0.4.13 yesterday and it's still happening.  Never used strongcoin and the addresses I'm using have never been in another client.
It (one peer, not in blockchain) was lasting about 60-90 minutes, but my first send with 0.4.13 has been stuck this way for just over two hours now. Several transactions never propagated at all and I needed to reebuild the blockchain to "free up" those coins.
What more information is needed (steps to be taken) to get out of the land of "If the transaction is not found then it indicates that the transaction was never sent properly, the transaction never propagated (perhaps a double spend) or some other reason. This needs more information to track down."?
-Aahz
What fee have you got set ?
If you have it less than 0.001 BTC you could well see delays in getting into a block because the miners choose other 'juicier' transactions. 
When you say 'it was lasting 60-90 minutes' are you saying that eventually it got into a block and showed up as confirmed in MultiBit ? Or does it never get confirmed ?
Also, where are your BTC coming from ? Are they mining dues ie coming from a coinbase ?
The fee is at MultiBit's default 0.0001, but the problem isn't getting confirmations, it's getting it recognized by the blockchain at all.
About half the time, after the 60-90 minutes it would finally show up at blockchain.info as unconfirmed.  Confirmation time is a whole different issue and clearly not a MultiBit issue.  The other half of the time it would go a day or more and I'd have to rebuild the blockchain in MultiBit to free up the coins.
The bitcoin came from various buyers of my products, donors to my websites, and bitcoin gambling sites or exchanges.  None came from mining.