Similar Threads:
1.problem configuring network ("host" works, "ping" doesn't)
Hi,
I just downloaded and installed my very first OpenSolaris... and have
problems with the very basic things like configuring network.
Overall, connectivity works, I can ping remote hosts using IP addresses.
Trying to ping using hostname (i.e. ping opensolaris.org) doesn't work -
ping says that the host is unknown.
On the other hand, "host opensolaris.org" returns a correct IP address -
which proves that DNS is set OK in /etc/resolv.conf.
What did I miss?
I noticed I had to correct /etc/nsswitch.conf (to use dns for hosts),
but other than that, I've no idea what I'm missing.
--
mg
2.ssh fails without prior ping or host ..
Hello NG,
what can be the cause for the following
ssh root@myHost
connect: no route to host
however thoese both work
ping myHost
ssh root@myHost
passwd:
or
host myHost
ssh root@myHost
passwd:
Regards, Daniel
3.pinging to neighbour host problem
Hello,
I am running ethereal on linux on pcs with pc1 with ip
address=192.18.1.250 and pc2 with ip=192.168.1.10. I am pinging from
pc1 to p2 but sometimes packet goes normal way and sometimes i think
frame corrupted. Following my capture znalysis ON PC2. First Frame is
corrupted why? frame5 correctly received.
what is the reason i am not able to receive frame correctly
sometimes?
Does following packet makes entry in ifconfig anyalysis. I check but
no counter increased on PC2.
Neither packet counted as RX packets nor dropped why?
eth1 Link encap:Ethernet HWaddr 00:08:A1:43:61:F5
inet addr:192.168.1.10 Bcast:192.168.1.255
Mask:255.255.255.0
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:33 errors:0 dropped:0 overruns:0 frame:0
TX packets:29 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txqueuelen:1000
RX bytes:3494 (3.4 Kb) TX bytes:2246 (2.1 Kb)
Interrupt:9 Base address:0x9c00
No. Time Source Destination
Protocol Info
1 0.000000 40:00:40:01:b6:54 45:00:00:54:00:00 0xc0a8
Ethernet II
Frame 1 (98 bytes on wire, 98 bytes captured)
Arrival Time: May 20, 2005 15:57:13.599959000
Time delta from previous packet: 0.000000000 seconds
Time since reference or first frame: 0.000000000 seconds
Frame Number: 1
Packet Length: 98 bytes
Capture Length: 98 bytes
Protocols in frame: eth:data
Ethernet II, Src: 40:00:40:01:b6:54, Dst: 45:00:00:54:00:00
Destination: 45:00:00:54:00:00 (45:00:00:54:00:00)
Source: 40:00:40:01:b6:54 (40:00:40:01:b6:54)
Type: Unknown (0xc0a8)
Data (84 bytes)
0000 45 00 00 54 00 00 40 00 40 01 b6 54 c0 a8 01 fa
E..T..@.@..T....
0010 c0 a8 01 0a 08 00 df 9d 52 0e 00 01 22 bf 8d 42
........R..."..B
0020 1e 4e 0d 00 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13
.N..............
0030 14 15 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 ............
!"#
0040 24 25 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33
$%&'()*+,-./0123
0050 34 35 36 37 00 00 00 00 00 00 00 00 00 00 00 00
4567............
0060 00 00 ..
Frame 5 (98 bytes on wire, 98 bytes captured)
Arrival Time: May 20, 2005 16:12:42.872068000
Time delta from previous packet: 177.629913000 seconds
Time since reference or first frame: 182.659884000 seconds
Frame Number: 5
Packet Length: 98 bytes
Capture Length: 98 bytes
Protocols in frame: eth:ip:icmp:data
Ethernet II, Src: 00:08:a1:43:62:91, Dst: 00:08:a1:43:61:f5
Destination: 00:08:a1:43:61:f5 (192.168.1.10)
Source: 00:08:a1:43:62:91 (CnetTech_43:62:91)
Type: IP (0x0800)
Internet Protocol, Src Addr: 192.168.1.250 (192.168.1.250), Dst Addr:
192.168.1.10 (192.168.1.10)
Version: 4
Header length: 20 bytes
Differentiated Services Field: 0x00 (DSCP 0x00: Default; ECN: 0x00)
0000 00.. = Differentiated Services Codepoint: Default (0x00)
.... ..0. = ECN-Capable Transport (ECT): 0
.... ...0 = ECN-CE: 0
Total Length: 84
Identification: 0x0000 (0)
Flags: 0x04 (Don't Fragment)
0... = Reserved bit: Not set
.1.. = Don't fragment: Set
..0. = More fragments: Not set
Fragment offset: 0
Time to live: 64
Protocol: ICMP (0x01)
Header checksum: 0xb654 (correct)
Source: 192.168.1.250 (192.168.1.250)
Destination: 192.168.1.10 (192.168.1.10)
Internet Control Message Protocol
Type: 8 (Echo (ping) request)
Code: 0
Checksum: 0xdf9d (correct)
Identifier: 0x520e
Sequence number: 0x0001
Data (56 bytes)
0000 00 08 a1 43 61 f5 00 08 a1 43 62 91 08 00 45 00
...Ca....Cb...E.
0010 00 54 00 00 40 00 40 01 b6 54 c0 a8 01 fa c0 a8
.T..@.@..T......
0020 01 0a 08 00 df 9d 52 0e 00 01 22 bf 8d 42 1e 4e
......R..."..B.N
0030 0d 00 08 09 0a 0b 0c 0d 0e 0f 10 11 12 13 14 15
................
0040 16 17 18 19 1a 1b 1c 1d 1e 1f 20 21 22 23 24 25 ..........
!"#$%
0050 26 27 28 29 2a 2b 2c 2d 2e 2f 30 31 32 33 34 35
&'()*+,-./012345
0060 36 37 67
4.arp problem in pinging host
[Removed comp.protocols.tcp-ip since it isn't relevant]
I guess I should have asked for ifconfig -a in the same post -
newsreader won't let me go back and look at original. Anyway
> Routing table for hostA
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth0
> 172.16.1.0 192.168.1.1 255.255.255.0 UG 0 0 0
> eth0
OK but redundant, since it is covered by the default route.
> 0.0.0.0 192.168.1.1 0.0.0.0 UG 0 0 0
> eth0
So eth0 has an IP addr of 192.168.1.x where x != 1, and is connected by
a crossover cable to eth1 on R1. eth1 on R1 has address 192.168.1.1.
OK so far?
> Routing table for R1
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth1
> 172.16.1.0 0.0.0.0 255.255.255.0 UG 0 0 0 eth0
Redundant.
> 10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
> eth0
> 0.0.0.0 10.1.1.100 0.0.0.0 UG 0 0 0
> eth0
eth1 had address 192.168.1.1 and is connected to A.
eth0 has address 10.1.1.1 and is connected to R2. More on this later.
>
> I have also crosscable connection of R1 to another R2 with routing
> table
> Kernel IP routing table
> Destination Gateway Genmask Flags Metric Ref Use
> Iface
> 192.168.1.0 0.0.0.0 255.255.255.0 U 0 0 0
> eth0
> 172.16.1.0 0.0.0.0 255.255.255.0 UG 0 0 0 eth1
> 10.0.0.0 0.0.0.0 255.0.0.0 U 0 0 0
> eth0
> 0.0.0.0 10.1.1.1 0.0.0.0 UG 0 0 0
> eth0
eth0 has address 10.1.1.100 and is connected to R1 via crossover cable?
I see several things wrong with this. First, R1 and R2 send default
traffic to each other. Second, it would be more usual to use a netmask
of 255.255.255.0 for the 10.1.1.0 network. Third, I don't understand
how the 192.168.1 entry got here or what it is supposed to be doing.
(There are two wildly different networks assigned to the same interface
with no gateway on either entry.) The 172.16.1.0 entry looks funny too.
What is the address of eth1 supposed to be?
I think you need to sit down with a piece of paper and draw your
network. For each network segment (each crossover cable is one) write
in the interface name, the addresses of each interface, the network
address, the broadcast address and the netmask. Then double check that
the routing tables and addresses (output of ifconfig -a or equivalent)
match the diagram.
5.Can ping on both ip and host name but nbtstat -a gets "host not found"
We have 2 servers with NT4 that we are trying to install Symantec antivirus 8,1 with another server as parent server and it fails because the server can not be found
Doing a Ping from the server that we are trying to install on works fine on both IPadress and host name but trying to do a nbtstat -a ends up with a "host not found !!
All IP-configurations are correct on both servers and is the same as all our servers where we had no problems doing the SAV installation
I dont have a clue what causes this and i wonder if someone else has an idea
//Thomas
6. Pinging Host Names as opposed to pinging FQDNs
7. ping hostname failed while ping IP_Address working Options
8. ping from vxsim to host linux machine