Sponsored Content
Top Forums UNIX for Advanced & Expert Users Unable to connect to Sunfire v215 box via XStart Post 302354674 by System Shock on Saturday 19th of September 2009 10:21:35 AM
Old 09-19-2009
Code:
C:\Documents and Settings\Administrator>pathping 10.8.104.51
Tracing route to 10.8.104.51 over a maximum of 30 hops
0 GSS-AERO-TEST.savilab.com [10.8.108.136]
1 10.8.108.2
2 * * *

If pathping is anything like traceroute, your Windows server is not even seeing its gateway. Could be the Windows server's routing config was changed, could be the ethernet cable, could be the switch, the switch port...
 

10 More Discussions You Might Find Interesting

1. OS X (Apple)

open ssh port (22) to connect to other box

Hi Do I have to open my ssh port if I like to connect to another machine? - if yes, how? Or is that only if I want to access my one computer from the outside? I run Mac OS 10.4 and like to access a unix box on the other side. /andreas (1 Reply)
Discussion started by: lulle
1 Replies

2. Shell Programming and Scripting

How to COnnect to Oracle database from UNIX Box

I am trying to connect to Oracle Databse from UNIX box using sqlplus command. But i get sqplus not found message. $ sqlplus sqlplus: not found I have searched in forums and all are suggesting to set environment varaibles...can somebody tell me what variables to set and how to set.and the... (12 Replies)
Discussion started by: angelarosh
12 Replies

3. Shell Programming and Scripting

Connect to database from different unix box

Hi Friends, I have a one unix box "x.y.z" on SunOS , where oracle is not installed. And another machine "a.b.c" on AIX , where oracle is installed. Now i want to make a script on x.y.z , that can connect to database on a.b.c, using sqlplus command. and then generate a report based on the... (5 Replies)
Discussion started by: gauravgarg
5 Replies

4. Solaris

Sunfire 490 connect to IBM SAN DS4000

Hi All Recently i plan use our company Sunfire V490 to hook up the IBM SAN Storage DS4000. But i not sure is it got any requirement to do this, is it need any extra driver, equipment??? hope can get some advice from here.. Kindly advise. Thanks all (3 Replies)
Discussion started by: SmartAntz
3 Replies

5. Emergency UNIX and Linux Support

Unable to connect using SFTP

I shall explain the situation that I am facing to the best extent possible. I require some help, as this situation is an urgent one. I am trying to automate sending data from one AIX machine to another. A script runs that tries to push data received from an upstream application to another AIX... (7 Replies)
Discussion started by: ggayathri
7 Replies

6. Solaris

how to connect to wireless from virtual box

hi everyone... this is my first post here please help me with this..as iam new to solaris i have installed solaris 10 on virtual box.. and am not able to connect to the internet .. is there anyway i can get connect to the net.. please help me step by step if possible... thanks in... (1 Reply)
Discussion started by: yrajendergoud
1 Replies

7. Shell Programming and Scripting

connect Clearcase from unix box

Hi am using unix box and am always download code from clearcase. I need to connect clearcase server from my unix box using shell script.I need to create view baseline everything using the sript. am not mention I need a code. Just anyone help me start the concept to write a code. Thanks,... (1 Reply)
Discussion started by: ckchelladurai
1 Replies

8. HP-UX

Unable to connect SSH from HP-UX

Hi, I'm trying to connect from an HP-UX with SSH2 client(ssh2 3.1.2 on hppa1.1-hp-hpux11.00) to an SSH2 server on a VxWorks system. The SSH connection is failing with the below connection logs: > /usr/local/bin/ssh2 -v -l testuser 10.10.10.10 debug: Ssh2/ssh2.c:1391: Using file... (4 Replies)
Discussion started by: ysafi
4 Replies

9. UNIX for Dummies Questions & Answers

[Solved] Box with a new MAC address can't connect to the internet

Hi, i replaced one of my UNIX machines last week, the old box had an external IP address before. Everything is the same as the previous box and the only difference is the new one has a different MAC address (of course, since the mother boards are different). The problem is the new machine can't... (2 Replies)
Discussion started by: tezarin
2 Replies

10. Red Hat

Unable to connect to internet

Hello, I just installed CentOS 7 (Server with GUI) and guess what I could install Virtual Box Guest additions without installing any extra package/software which is great news ! Now bad news or not so great news. My Host OS is Windows 10, Virtual Box is the virtualization software. CentOS7-1... (0 Replies)
Discussion started by: bluemind2005
0 Replies
TRACEROUTE6(8)						      System Manager's Manual						    TRACEROUTE6(8)

NAME
rltraceroute6 - IPv6 traceroute tool tcptraceroute6 - TCP/IPv6 traceroute tool SYNOPSIS
traceroute6 [-AdEILlnrSU] [-f min_hop] [-g hop] [ -i iface] [-m max_hop] [-p port] [-q attempts] [ -s source] [-t tclass] [-w wait] [-z delay_ms] < hostname/address> [packet length] tcptraceroute6 [-AdEnrS] [-f min_hop] [-g hop] [ -i iface] [-l packet_size] [-m max_hop] [-p port] [ -q attempts] [-s source] [-t tclass] [-w wait] [ -z delay_ms] < hostname/address> [port] DESCRIPTON
rltraceroute6 is an IPv6 traceroute implementation. It displays the list of hops along the network route between the local system and specified destination, by sending packets while incre- menting their hop limit, until the final destination is reached. By default, rltraceroute6 sends UDP probe packets toward the destination (that's the historical default). However, it can also send TCP packets, much like Michael C. Toren's tcptraceroute does on IPv4 networks; tcptraceroute6 sends TCP packets by default (and mimics tcp- traceroute command line syntax). Finally, it can also send ICMPv6 Echo Request packets, like some other traceroute implementations (such as the one in Microsoft Windows); tracert6 does this by default. You must specify the name or address of the host toward which the network route should be determined. An optional additional parameter specifies either the probe packets length (for UDP and ICMP packets), or the destination port number/service name (for TCP packets). Note that TCP destination port zero really is TCP port numbered 0 (which cannot be used via the standard higer-level TCP/IP programming interface). OPTIONS
-A Send TCP/ACK probe packets. That's very efficient against stateless firewalls (e.g. the official Linux kernel versions up to and including 2.4.31 and 2.6.14), and utterly helpless against stateful ones. Note that TCP/ACK probing cannot determine whether the destination TCP port is open or not. -d Enable socket debugging option (SO_DEBUG). Unless you are debugging the kernel, this is probably not going to have any actual effect. -E Send ECN-setup TCP/SYN probe packets (as per RFC 3168) rather than non-ECN-setup TCP/SYN probe packets. This has no effect unless command line optin -S is specified as well. -F This option is ignored for backward compatibility. IPv6 packets are never fragmented en route. -f Override the initial IPv6 packets hop limit (default: 1). -g Add an IPv6 route segment within an IPv6 Routing Header. This enables loose source routing. Currently, only "Type 0" routing header is supported. -h Display some help and exit. -I (rltraceroute6 only) Send ICMPv6 Echo requests (like ping6) as probe packets. That's the default for tracert6. -i Only send packets through the specified interface. See also BUGS. -I (rltraceroute6 only) Send UDP-Lite (protocol 136) packets (with full checksum coverage) as probe packets instead of normal UDP (protocol 17). -l (rltraceroute6 only) Print the hop limit of received packets. This is mostly used to detect asymmetric routing. -l (tcptraceroute6 only) Specify the size (bytes) of sent packets. -m Override the maximum hop limit (maximum number of hops). The default is 30 hops which should be sufficient on the IPv6 Internet for some time. -N Try to resolve each hop's IPv6 address to a host name. This is the default. This option is meant for backward compatibility with tcptraceroute(8). -n Do not try to resolve each hop's IPv6 address to a host name. That may speed up the traceroute significantly. -p For rltraceroute6, specify the base destination port number (default: 33434). rltraceroute6 assumes that packets toward this port up to this port plus the maximum hop limit are not in use by any program on the final destination and that they are not blocked by some firewall. The fact that this very assumption was not always correct, eventually lead to the development of the original IPv4 tcptraceroute by Michael Toren. For tcptraceroute6, specify the source port number (default: auto). Note that source port number zero really means number zero, rather than some port number that would be automatically assigned, as is the case with usual softwares. -q Override the number of probes sent to each hop (default: 3). -r Do not route packets, i.e. do not send packets through a gateway that would be specified by the routing table. See also BUGS. -S Use TCP/SYN probe packets. That's the default for tcptraceroute6. -s Specify the source address to use for probe packets explicitly. -S Use UDP probe packets. That's the default for rltraceroute6. -t Specify the traffic class (DSCP) for probe packets. See also BUGS. -U (rltraceroute6 only) Send UDP probe packets. That's the default. -V Display program version and license and exit. -w Override the delay (in seconds) to wait for response once a given probe packet was sent (default: 5 seconds). -x This option is ignored for seamless migration from IPv4 traceroute. The IPv6 header has no checksum field. -z Specify a milliseconds delay to wait between each probe with identical hop limit. This can be useful to work-around ICMPv6 rate limitation on some hosts. DIAGNOSTICS
If a response is received, the round-trip time is printed. In addition, specific symbols denote certain errors: * No response No valid response received before the timeout delay (see -w option). !N No route to destination There is no entry for the destination network in the routing table. !A Communication with destination administratively prohibited A firewall explicitly rejected the traffic. !S Beyond scope of source address The address scope of the source address is too small to reach the destination address. At the time of writing, this can only happen when using a link-local source address to reach a global scope destination. (Note: some IPv4 traceroute implementations use !S for source route error which is completely different) !H Address unreachable The host address is not reachable for some other reasons, particularly a link-layer failure (e.g. Neighbor discovery failure). !P Unrecognized Next Header type encountered The destination does not implement the layer-4 protocol used. You should retry with ICMPv6 Echo Requests (-I command line option) which MUST be supported by any IPv6 node. SECURITY
rltraceroute6 should be setuid root to allow use by non privileged users. It will drop its root privileges before any attempt is made to send or receive data from the network so as to reduce the possible impact of a security vulnerability. BUGS
However useful they might be, -i and -r options are ignored by the official Linux kernel at the time of writing this manpage, and hence do not work as documented. Support for option -t was broken until Linux kernel version 2.6.18. Usage of Routing Header, with option -g, triggers an OOPS on Linux kernel versions below 2.6.17.12. Receiving TCP/SYN-ACK packets does not work on FreeBSD at all. This severely limits the usefulness of tcptraceroute6 on FreeBSD. Packet length takes the IPv6 header and, if present, extension headers into account. rltraceroute6 versions before 0.7.4 used it as IPv6 payload length instead, i.e. did not include the layer-3 headers in the computation. Linux iputils traceroute6 does not even include the UDP header. On the whole, the packet length semantic is very inconsistent among IPv6 traceroute implementations. SEE ALSO
ipv6(7), traceroute(8), tcptraceroute(8), traceroute6(8) AUTHOR
Remi Denis-Courmont <remi at remlab dot net> $Id: rltraceroute6.8 658 2010-10-31 20:56:30Z remi $ http://www.remlab.net/ndisc6/ traceroute6 $Date: 2010-10-31 22:56:30 +0200 (dim. 31 oct. 2010) $ TRACEROUTE6(8)
All times are GMT -4. The time now is 03:32 PM.
Unix & Linux Forums Content Copyright 1993-2022. All Rights Reserved.
Privacy Policy