M Lu wrote:
I helped a friend of mine to have his Web Server running on DMZ network.
It used to work OK until now. I just know that he has changed his
network card on the Web Server machine, but everything seems fine when
he accesses his machine locally. I can also access that machine via
Tom Eastep wrote:
M Lu wrote:
I helped a friend of mine to have his Web Server running on DMZ
network. It used to work OK until now. I just know that he has changed
his network card on the Web Server machine, but everything seems fine
when he accesses his machine locally. I can also access that
Tom Eastep wrote:
After I sent this, I realized that it is probably nonsense since the SYN
is reaching the server. I would still make sure that the SYN,ACK has the
proper ethernet destination address though...
Another piece of advice -- *Always* use the -n option when using
tcpdump; otherwise,
Thank you Tom for your advice. When using '-n' with tcpdump, the IP has been
printed and it also looks good. Well, I will try to ask him to replace the
DMZ machine with another one for testing and see if the problem goes away.
Thanks again, Tom.
--
tcpdump -n -i eth2 host 24.61.157.240
M Lu wrote:
Thank you Tom for your advice. When using '-n' with tcpdump, the IP has
been printed and it also looks good. Well, I will try to ask him to
replace the DMZ machine with another one for testing and see if the
problem goes away.
Thanks again, Tom.
--
tcpdump -n -i eth2 host
