01-26-2006
can ping but can not telnet UNIX
I have one problem and it is giving me hard time
I can ping my windows machine
root@x1ChXpress:/sbin
>ping 192.168.129.66
192.168.129.66 is alive
root@x1ChXpress:/sbin
>netstat -rn
Routing Table:
Destination Gateway Flags Ref Use Interface
-------------------- -------------------- ----- ----- ------ ---------
172.16.0.148 164.48.156.180 UGH 0 37
192.168.129.66 164.48.156.166 UGH 0 7
192.168.129.134 164.48.156.166 UGH 0 15
164.48.152.0 164.48.156.169 U 3 39949 hme0
224.0.0.0 164.48.156.169 U 3 0 hme0
default 164.48.156.166 UG 0 81738
127.0.0.1 127.0.0.1 UH 0 900564 lo0
also I can ping my Unix from windows machine IP 195.168.128.123 DG 192.168.128.1
but I can not connect telnet from windows to UNIX
what might be a problem
thanks
10 More Discussions You Might Find Interesting
1. IP Networking
I can ping other computers in my office. I can telnet other users in my office but i cannot get out of the office network. If i try to go out side of my network it cannot find host.
Any ideas? (5 Replies)
Discussion started by: macdonto
5 Replies
2. SCO
Hi,
Can anybody help me out why l can't not ping my server with Openserver 5.0.4 with my windows machine from a remote site.
The machine could see the local LAN with the Router however, i can't ping or telnet unto the server from another site on the WAN. The default gateway was configure on the... (0 Replies)
Discussion started by: kayode
0 Replies
3. AIX
Hi All,
We are not able to ping to a AIX box...Network is ok..when we give ping from that AIX box..it is giving 0821-067 ping: The socket creation call failed.there is no enough buffer space for the requested socket operation.
refresh -s inetd is also giving socket error.
Please help to... (1 Reply)
Discussion started by: b_manu78
1 Replies
4. Infrastructure Monitoring
We have a Sun Solaris Netra 20 server. Our O&M Server gets Alarm Processor
not responding. When Alarm occurs, you can ping the sun server but cannot telnet it. We keep getting Interrupt level not serviced. var/adm/message log is
> tail -f messages
Apr 12 20:09:56 cama pcisch: PCI-device:... (9 Replies)
Discussion started by: krabu
9 Replies
5. UNIX for Dummies Questions & Answers
Hello for all!
This is the situation:
I must create many users that only can execute telnet and ping.
Create users is not a problem, but I donīt know how limit the users privileges, to only execute telnet and ping.
I hope you can help me.
Thank's for all.
Bye :)
PD: Sorry for my... (4 Replies)
Discussion started by: bobbasystem
4 Replies
6. UNIX for Advanced & Expert Users
Hi all,
I am not sure if my problem is specific to HP-UX or not. Hopefully someone can tell me what's wrong.
I have a server name server1 10.100.50.10 in the /etc/hosts file and if I do a ping server1, it shows the right IP address.
However, if I run telnet server1, it is not using... (4 Replies)
Discussion started by: newbie_01
4 Replies
7. AIX
Hi,
After a crash of our older AIX server it happend as it is in the title:
ping is ok, but telnet:
What it can be this strange thing?
Franci (2 Replies)
Discussion started by: frajer
2 Replies
8. UNIX for Dummies Questions & Answers
can you provide the command in solaris8 if I wanted to ping,telnet, traceroute an IP address with a port? thanks (1 Reply)
Discussion started by: lhareigh890
1 Replies
9. Shell Programming and Scripting
Hello,
I need help, I have the following which save in the result file ping and telnet:port test.
Basically the script works but I should implement a check on ping and telnet command so that ping has 5 seconds threshold and telnet (more important) 10 seconds. Over that threshold ping and... (0 Replies)
Discussion started by: marmellata
0 Replies
10. BSD
I put this thread to shell and bsd, because I want to resolve this matter on bsd.
May somebody can explain to me how to ping a remote server, in unix. BTW the following code examples were tried on a linux system as well, with the same output, nothing. But on my bsd are not installed nmap neither... (4 Replies)
Discussion started by: 1in10
4 Replies
LEARN ABOUT DEBIAN
shorewall-exclusion
SHOREWALL-EXCLUSION(5) [FIXME: manual] SHOREWALL-EXCLUSION(5)
NAME
exclusion - Exclude a set of hosts from a definition in a shorewall configuration file.
SYNOPSIS
!address-or-range[,address-or-range]...
!zone-name[,zone-name]...
DESCRIPTION
The first form of exclusion is used when you wish to exclude one or more addresses from a definition. An exclaimation point is followed by
a comma-separated list of addresses. The addresses may be single host addresses (e.g., 192.168.1.4) or they may be network addresses in
CIDR format (e.g., 192.168.1.0/24). If your kernel and iptables include iprange support, you may also specify ranges of ip addresses of the
form lowaddress-highaddress
No embedded whitespace is allowed.
Exclusion can appear after a list of addresses and/or address ranges. In that case, the final list of address is formed by taking the first
list and then removing the addresses defined in the exclusion.
Beginning in Shorewall 4.4.13, the second form of exclusion is allowed after all and any in the SOURCE and DEST columns of
/etc/shorewall/rules. It allows you to omit arbitrary zones from the list generated by those key words.
Warning
If you omit a sub-zone and there is an explicit or explicit CONTINUE policy, a connection to/from that zone can still be matched by the
rule generated for a parent zone.
For example:
/etc/shorewall/zones:
#ZONE TYPE
z1 ip
z2:z1 ip
...
/etc/shorewall/policy:
#SOURCE DEST POLICY
z1 net CONTINUE
z2 net REJECT
/etc/shorewall/rules:
#ACTION SOURCE DEST PROTO DEST
# PORT(S)
ACCEPT all!z2 net tcp 22
In this case, SSH connections from z2 to net will be accepted by the generated z1 to net ACCEPT rule.
In most contexts, ipset names can be used as an address-or-range. Beginning with Shorewall 4.4.14, ipset lists enclosed in +[...] may also
be included (see shorewall-ipsets[1] (5)). The semantics of these lists when used in an exclusion are as follows:
o !+[set1,set2,...setN] produces a packet match if the packet does not match at least one of the sets. In other words, it is like NOT
match set1 OR NOT match set2 ... OR NOT match setN.
o +[!set1,!set2,...!setN] produces a packet match if the packet does not match any of the sets. In other words, it is like NOT match set1
AND NOT match set2 ... AND NOT match setN.
EXAMPLES
Example 1 - All IPv4 addresses except 192.168.3.4
!192.168.3.4
Example 2 - All IPv4 addresses except the network 192.168.1.0/24 and the host 10.2.3.4
!192.168.1.0/24,10.1.3.4
Example 3 - All IPv4 addresses except the range 192.168.1.3-192.168.1.12 and the network 10.0.0.0/8
!192.168.1.3-192.168.1.12,10.0.0.0/8
Example 4 - The network 192.168.1.0/24 except hosts 192.168.1.3 and 192.168.1.9
192.168.1.0/24!192.168.1.3,192.168.1.9
Example 5 - All parent zones except loc
any!loc
FILES
/etc/shorewall/hosts
/etc/shorewall/masq
/etc/shorewall/rules
/etc/shorewall/tcrules
SEE ALSO
shorewall(8), shorewall-accounting(5), shorewall-actions(5), shorewall-blacklist(5), shorewall-hosts(5), shorewall_interfaces(5),
shorewall-ipsets(5), shorewall-maclist(5), shorewall-masq(5), shorewall-nat(5), shorewall-netmap(5), shorewall-params(5),
shorewall-policy(5), shorewall-providers(5), shorewall-proxyarp(5), shorewall-rtrules(5), shorewall-routestopped(5), shorewall-rules(5),
shorewall.conf(5), shorewall-secmarks(5), shorewall-tcclasses(5), shorewall-tcdevices(5), shorewall-tcrules(5), shorewall-tos(5),
shorewall-tunnels(5), shorewall-zones(5)
NOTES
1. shorewall-ipsets
http://www.shorewall.net/manpages/shorewall-ipsets.html
[FIXME: source] 06/28/2012 SHOREWALL-EXCLUSION(5)