Re: iptables forwarding question

From: James Pifer <jep@xxxxxxxxxxxxxxxx>
Date: Fri, 17 Mar 2006 16:32:36 -0500

No, I sure didn't give much info.

I don't have access to server2.

Not a ton of suggestions based on what you sent. Try 'ping'ing server2.
Your log suggests you may have noticable packet loss. 'ping' will tell you
if that is your problem.

- Benjamin Franz

I had a chance to do this right now on a windows machine. I let it ping
40 or 50 times. It had one little hiccup in the middle, but otherwise
seemed ok. The response times are about the same as what I see on my
linux machine that is the router.

Thanks,
James

Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Reply from server2: bytes=32 time=128ms TTL=57
Reply from server2: bytes=32 time=112ms TTL=57
Reply from server2: bytes=32 time=125ms TTL=57
Reply from server2: bytes=32 time=142ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=122ms TTL=57
Reply from server2: bytes=32 time=118ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=114ms TTL=57
Reply from server2: bytes=32 time=118ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=116ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Reply from server2: bytes=32 time=121ms TTL=57
Reply from server2: bytes=32 time=128ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=111ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Request timed out.
Reply from server2: bytes=32 time=418ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=122ms TTL=57
Reply from server2: bytes=32 time=119ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=114ms TTL=57
Reply from server2: bytes=32 time=116ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=120ms TTL=57
Reply from server2: bytes=32 time=112ms TTL=57
Reply from server2: bytes=32 time=112ms TTL=57
Reply from server2: bytes=32 time=120ms TTL=57
Reply from server2: bytes=32 time=116ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=114ms TTL=57
Reply from server2: bytes=32 time=132ms TTL=57
Reply from server2: bytes=32 time=116ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=115ms TTL=57
Reply from server2: bytes=32 time=116ms TTL=57
Reply from server2: bytes=32 time=116ms TTL=57
Reply from server2: bytes=32 time=118ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=123ms TTL=57
Reply from server2: bytes=32 time=120ms TTL=57
Reply from server2: bytes=32 time=117ms TTL=57
Reply from server2: bytes=32 time=139ms TTL=57

--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Follow-Ups:
- Re: iptables forwarding question
  - From: Myth User

References:
- iptables forwarding question
  - From: James Pifer
- Re: iptables forwarding question
  - From: Benjamin Franz
- Re: iptables forwarding question
  - From: James Pifer
- Re: iptables forwarding question
  - From: Benjamin Franz
- Re: iptables forwarding question
  - From: James Pifer
- Re: iptables forwarding question
  - From: Benjamin Franz

Prev by Date: Wine and Timbuktu 5.1
Next by Date: Re: FC5 release question
Previous by thread: Re: iptables forwarding question
Next by thread: Re: iptables forwarding question
Index(es):
- Date
- Thread

Relevant Pages

Re: tcp/ip vs named pipes
... I have never had contact with sql server before. ... I can ping, but can't telnet on port 1433. ... test is can it ping Server2 by name. ...
(microsoft.public.sqlserver.clients)
Re: tcp/ip vs named pipes
... The first question is whether App2 can find Server2. ... test is can it ping Server2 by name. ...
(microsoft.public.sqlserver.clients)
One way ping!
... Now and then "Server2" cannot ping (by name or ip ... Any other address both LAN and WAN. ... Basically its a one way ping ...
(microsoft.public.windows.server.general)
Re: Client Logon question when you have 2 domains?
... can you ping the server2 by IP when you have two domains on? ... When both servers are on the network outlook can't connect to the exchange ... I don't understand why I can't connect to server2 on domain AJ2 that has ...
(microsoft.public.windows.server.sbs)