sunhux
asked on
Will winpcap & tracetcp cause any problem to Netbackup & Win 2008
http://tracetcp.sourceforge.net/
I'm contemplating to install tracetcp on our Netbackup NBU 7.1
media server but tracetcp requires winpcap.
As it's a production media server (& I can't have a laptop or
test server on this LAN switch anymore), any concern that
winpcap or tracetcp will cause a problem to the NIC/OS/
backup jobs?
We have been facing intermittent ftp job failures between
2 separate sites that goes through WAN & there's at least
9 hops between the ftp client & server.
'ping -r .....' uses icmp which may not show the hop where
the problem lies & I thought of using tracetcp to simulate
tcp21 (ie as closely as possible to ftp)
I'm contemplating to install tracetcp on our Netbackup NBU 7.1
media server but tracetcp requires winpcap.
As it's a production media server (& I can't have a laptop or
test server on this LAN switch anymore), any concern that
winpcap or tracetcp will cause a problem to the NIC/OS/
backup jobs?
We have been facing intermittent ftp job failures between
2 separate sites that goes through WAN & there's at least
9 hops between the ftp client & server.
'ping -r .....' uses icmp which may not show the hop where
the problem lies & I thought of using tracetcp to simulate
tcp21 (ie as closely as possible to ftp)
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I also find 'tracert destination_IP" is rather slow,
instead "tracert -d ..." is much faster
instead "tracert -d ..." is much faster
ASKER
Not quite answered
ASKER
When the ftp got disconnected, the 'tracert -d ..." & ping (a script
that pings every single hop on the MetroWAN), did not show any
problem/timeout at all.
Now I found I can't do 'tracetcp ...' on the network as SYN packets
are blocked on the MetroWAN
Is there any freeware ftp client which could do a 'low-bandwidth'
ftp to simulate & capture a full trace so that we could narrow
down if this is a Telco, the remote end ftp or the switches/router/
firewalls in between that's causing the occasional disconnects?
that pings every single hop on the MetroWAN), did not show any
problem/timeout at all.
Now I found I can't do 'tracetcp ...' on the network as SYN packets
are blocked on the MetroWAN
Is there any freeware ftp client which could do a 'low-bandwidth'
ftp to simulate & capture a full trace so that we could narrow
down if this is a Telco, the remote end ftp or the switches/router/
firewalls in between that's causing the occasional disconnects?
ASKER
not quite answered
ASKER
tracetcp destination_IP:ftp
to simulate a true ftp packet ?