On 03.07.2014 03:53, Bill Oliver wrote:
On Thu, 3 Jul 2014, poma wrote:
Yeah, it would be good to hear from the service provider that everything is
OK on their side, so you're 120% sure.
It is always good practice.
poma,
Actually, cotse.net is one of the more responsive companies I've dea
On Thu, 3 Jul 2014, poma wrote:
Yeah, it would be good to hear from the service provider that everything is
OK on their side, so you're 120% sure.
It is always good practice.
poma,
Actually, cotse.net is one of the more responsive companies I've dealt
with. They don't do much hand-holdi
On 03.07.2014 02:28, Bill Oliver wrote:
On Wed, 2 Jul 2014, poma wrote:
No joy. I have a support call into my virtual machine vendor. I'll see
if they have any words of wisdom.
billo
Which virtual machine vendor?
poma
Cotse.net
billo
Yeah, it would be good to hear from the
On 03.07.2014 02:51, Bill Oliver wrote:
On Wed, 2 Jul 2014, Bill Oliver wrote:
No joy. I have a support call into my virtual machine vendor. I'll see
if they have any words of wisdom.
billo
Well, for what it's worth, I still don't know why this happens but:
1) My vendor hasn't changed
On Wed, 2 Jul 2014, Bill Oliver wrote:
No joy. I have a support call into my virtual machine vendor. I'll see
if they have any words of wisdom.
billo
Well, for what it's worth, I still don't know why this happens but:
1) My vendor hasn't changed anything recently.
2) On the target mach
On Wed, 2 Jul 2014, poma wrote:
No joy. I have a support call into my virtual machine vendor. I'll see
if they have any words of wisdom.
billo
Which virtual machine vendor?
poma
Cotse.net
billo
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscript
On 02.07.2014 22:43, Bill Oliver wrote:
On Wed, 2 Jul 2014, Rick Stevens wrote:
I hit a similar thing on my F19 machine. The fix I had was (as root):
echo "0" >/proc/sys/net/ipv4/tcp_sack
(I did this on the advice of our in-house network guru) I then added
these to the end of my /etc
On Wed, 2 Jul 2014, Rick Stevens wrote:
I hit a similar thing on my F19 machine. The fix I had was (as root):
echo "0" >/proc/sys/net/ipv4/tcp_sack
(I did this on the advice of our in-house network guru) I then added
these to the end of my /etc/sysctl.conf file so it gets set on the n
On 07/02/2014 06:49 AM, Bill Oliver issued this missive:
Another update. It only happens when trying to send to my virtual
machine -- I can ftp to at least two other places just fine using vpn.
I hit a similar thing on my F19 machine. The fix I had was (as root):
echo "0" >/proc/sys/
Another update. It only happens when trying to send to my virtual machine -- I
can ftp to at least two other places just fine using vpn.
billo
--
users mailing list
users@lists.fedoraproject.org
To unsubscribe or change subscription options:
https://admin.fedoraproject.org/mailman/listinfo/us
On Wed, 2 Jul 2014, Ed Greshko wrote:
On 07/02/14 10:51, Ed Greshko wrote:
On 07/02/14 09:36, Bill Oliver wrote:
227 Entering Passive Mode (50,7,12,26,124,13)
150 Ok to send data.
Hang!
Works fine if I don't use a vpn. I run a roundcube server on the same machine,
and I can download image
On 07/02/14 10:51, Ed Greshko wrote:
> On 07/02/14 09:36, Bill Oliver wrote:
>> 227 Entering Passive Mode (50,7,12,26,124,13)
>> 150 Ok to send data.
>>
>>
>> Hang!
>>
>> Works fine if I don't use a vpn. I run a roundcube server on the same
>> machine, and I can download images I receive in email
On 07/02/14 09:36, Bill Oliver wrote:
> 227 Entering Passive Mode (50,7,12,26,124,13)
> 150 Ok to send data.
>
>
> Hang!
>
> Works fine if I don't use a vpn. I run a roundcube server on the same
> machine, and I can download images I receive in emails using the roundcube
> server, even if I go t
Sigh. Another time the old "sudo yum update" breaks something...
All of a sudden, ftp does not work if I'm connected to the net using a
vpn. And it's very specific:
I can connect, log in, list a directory, etc. However, I can't "get" or
"mget" a file. Here's what happens:
[user@localhost ~
14 matches
Mail list logo
