Cannot ping host or guest using VM Workstation 5.5

Local host Machine Windows XP

VMWare Network Adpater VMNet1 (host)

IP 192.168.189.1

Adpater Ethernet Local machine

Suffix connection specific DNS: ISP

IP address: 192.168.1.101

VM guest computer

Ethernet adapter PB PVT:

Suffix connection specific DNS: white

IP address: 161.228.210.176

The network of the virtual computer is configured to use "Home" only

When I ping the host computer I get "Request timed out".

When I ping the Guest Machine (VM) I get "Request timed out".

Logon at the prompt, right click on 'My network places', choose 'Properties', right click on the connection to the local network and choose "Properties". Open the properties of "Internet (TCP/IP) Protocol". Select "Obtain an IP address automatically" and "Obtain DNS server address automatically". Let him.

If this does not work, provide "ipconfig/all" host AND guest, but also some screenshots of the tabs in the VMware virtual network Editor!

If you found this information useful, please consider awarding points to 'Correct' or 'Useful' responses Thank you!!

AWo

VCP / vEXPERT 2009

Tags: VMware

Similar Questions

Comments cannot ping host

Hi all:
I have a strange problem of networking that VMware technical support has not been able to help.
Summary of the problem: comments cannot ping host unless the host is a ping command, while the guest is ping to the host
Details of the problem: I have intalled VMware Workstation 6.5.2 on the host Windows Vista Edition Home Premium (SP1). I installed several guests, including Ubuntu 8.04, openSUSE 11, Win XP and Win 2000. All guests use "bridged" network. The host has a static IP address. All guests have DHCP. All these people have the same problem - they cannot ping the host. It simply returns "Destination unreachable". However, if I run a ping from the host (it didn't ping the same customer, any ip address on the network) while the guest is ping to the host, and then will cross ping of the guest. For the next two minutes, the guest will be able to ping the host without any problem (without 'help' of the host). Then the guest will again be able ping on the host and you will have to repeat the same process. Quite strange, isn't? Another problem, I can access the internet from the hosts and guests can ping each other. (I can't access the printer connected to the host. However if the guest can ping on the host, then it can also access the printer as well.) I tried everything but still can't find the root cause of the problem. Here is a list of the things I've tried:
1. tried VMware Workstation 6.5.2 on a Windows XP computer on the same network (equipped with a wireless card intel) and did NOT have this problem.
2. firewalls, antivirus software, VPN clients, etc. were all off. It did not help.
3. the problem disappears if I use the wired Ethernet connection
4. the current wireless adapter is a D-Link, but I also tried with a Linksys Wireless card and had the same problem
5. the same problem exists also for VMware 6.5.1
6. I have installed the software VirtuaBox VM from Sun and installed the same comments from Ubuntu on the same host. The problem goes away!
7. I also tried the "NAT" networking and had the same problem.
8. I also tried DHCP for host and had the same problem.
I've tried everything I can think of and nothing seemed to help. I have filed a request for assistance with VMware tech and traded a few emails with the support guy but have not heard from him for a few days. I would really appreciate if someone can offer a few ideas to help solve this problem. I'm not a networking guru, but I'm a software engineer, so you can talk to me in technical terms.
Thank you in advance.

Yes! as noted above, it is the arp tables.

my router is assigned the same IP address for the host computer and the guest, so as soon as you ping from your host prompt, the mac and ip is back in the arp (invites) tables and from there he will communicate via newly assigned ARP table. You can check this scathing the hostname and it will be the same ip address as your guest (in my case)

I then googled arp vmware and discovered that it is familir with chipset broadcom and vmware behavior.

ARP - a displays the tables,

ARP s 00-00-00-00-00-00 192.168.x.xxx - assign the IP address to a MAC address.

I hope this helps.

Cannot Ping hosts after you connect to ASA5500 using a client connection

I can ping hosts and gateways of the ASA5500, but after I connect I can't ping anything. The ASA5500 is connected to a layer 2 switch, this switch is shared resources for a layer 3. This 3 level switch is connected to another switch to level 3 where the gateways and hosts live. Again, I can ping hosts and gateways of the ASA5500 itself.

ASA Version 8.2 (5)
!
activate 8Ry2YjIyt7RRXU24 encrypted password
2KFQnbNIdI.2KYOU encrypted passwd
names of
!
interface GigabitEthernet0/0
nameif outside
security-level 0
IP address 208.19.xxx.xx 255.255.255.240
!
interface GigabitEthernet0/1
nameif inside
security-level 100
IP 10.47.146.199 255.255.255.0
!
interface GigabitEthernet0/2
Shutdown
No nameif
no level of security
no ip address
<--- more="" ---="">
!
interface GigabitEthernet0/3
Shutdown
No nameif
no level of security
no ip address
!
interface Management0/0
Shutdown
No nameif
no level of security
no ip address
!
passive FTP mode
DNS server-group DefaultDNS
permit same-security-traffic inter-interface
IP 10.47.138.0 allow Access - list extended SHEEP 255.255.255.0 172.16.1.0 255.255.255.0
IP 10.47.140.0 allow Access - list extended SHEEP 255.255.255.0 172.16.1.0 255.255.255.0
IP 10.47.141.0 allow Access - list extended SHEEP 255.255.255.0 172.16.1.0 255.255.255.0
IP 10.47.148.0 allow Access - list extended SHEEP 255.255.255.0 172.16.1.0 255.255.255.0
IP 10.47.149.0 allow Access - list extended SHEEP 255.255.255.0 172.16.1.0 255.255.255.0
IP 10.47.150.0 allow Access - list extended SHEEP 255.255.255.0 172.16.1.0 255.255.255.0
IP 10.47.151.0 allow Access - list extended SHEEP 255.255.255.0 172.16.1.0 255.255.255.0
IP 10.47.133.0 allow Access - list extended SHEEP 255.255.255.0 172.16.1.0 255.255.255.0
IP 10.47.212.0 allow Access - list extended SHEEP 255.255.255.0 172.16.1.0 255.255.255.0
IP 10.47.153.0 allow Access - list extended SHEEP 255.255.255.0 172.16.1.0 255.255.255.0
IP 10.47.157.0 allow Access - list extended SHEEP 255.255.255.0 172.16.1.0 255.255.255.0
IP 10.47.154.0 allow Access - list extended SHEEP 255.255.255.0 172.16.1.0 255.255.255.0
IP 10.47.146.0 allow Access - list extended SHEEP 255.255.255.0 172.16.1.0 255.255.255.0
pager lines 24
Within 1500 MTU
Outside 1500 MTU
mask 172.16.1.10 - 172.16.1.200 255.255.255.0 IP local pool VPNpool
no failover
ICMP unreachable rate-limit 1 burst-size 1
don't allow no asdm history
ARP timeout 14400
Global 1 interface (outside)
NAT (inside) 1 0.0.0.0 0.0.0.0
Route outside 0.0.0.0 0.0.0.0 208.19.xxx.xx 1
Route inside 10.47.133.0 255.255.255.0 10.47.146.1 1
Route inside 10.47.138.0 255.255.255.0 10.47.146.1 1
Route inside 10.47.140.0 255.255.255.0 10.47.146.1 1
Route inside 10.47.141.0 255.255.255.0 10.47.146.1 1
Route inside 10.47.148.0 255.255.255.0 10.47.146.1 1
Route inside 10.47.149.0 255.255.255.0 10.47.146.1 1
Route inside 10.47.150.0 255.255.255.0 10.47.146.1 1
Route inside 10.47.151.0 255.255.255.0 10.47.146.1 1
Route inside 10.47.153.0 255.255.255.0 10.47.146.1 1
Route inside 10.47.154.0 255.255.255.0 10.47.146.1 1
Route inside 10.47.157.0 255.255.255.0 10.47.146.1 1
Route inside the 10.47.212.0 255.255.254.0 10.47.146.1 1
Route inside the 10.47.214.0 255.255.254.0 10.47.146.1 1
Timeout xlate 03:00
Timeout conn 01:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02
Sunrpc timeout 0:10:00 h323 0:05:00 h225 mgcp from 01:00 0:05:00 mgcp-pat 0:05:00
Sip timeout 0:30:00 sip_media 0:02:00 prompt Protocol sip-0: 03:00 sip - disconnect 0:02:00
Timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute
timeout tcp-proxy-reassembly 0:01:00
Floating conn timeout 0:00:00
dynamic-access-policy-registration DfltAccessPolicy
No snmp server location
No snmp Server contact
life crypto ipsec security association seconds 28800
Crypto ipsec kilobytes of life - safety 4608000 association
Telnet timeout 5
SSH timeout 5
Console timeout 0
a basic threat threat detection
Statistics-list of access threat detection
no statistical threat detection tcp-interception
WebVPN
allow outside
SVC disk0:/anyconnect-win-3.1.04072-k9.pkg 1 image
enable SVC
tunnel-group-list activate
Anyconnect-policy group policy interns
Anyconnect-policy-strategy of group attributes
VPN - 100 simultaneous connections
VPN-idle-timeout no
Protocol-tunnel-VPN IPSec l2tp ipsec svc webvpn
WebVPN
SVC Dungeon-Installer installed
SVC request to enable default timeout 20 svc
username billuser1 password eS3lou7xhp / 8g 705 encrypted
username billuser1 attributes
type of remote access service
tunnel-group bill type remote access
tunnel-group invoice General attributes
address pool VPNpool
strategy-group-by default Anyconnect-policy
tunnel-group bill webvpn-attributes
activation of the Group billgroup_users alias
!
class-map inspection_default
match default-inspection-traffic
!
!
type of policy-card inspect dns preset_dns_map
parameters
maximum message length automatic of customer
message-length maximum 512
Policy-map global_policy
class inspection_default
inspect the preset_dns_map dns
inspect the ftp
inspect h323 h225
inspect the h323 ras
Review the ip options
inspect the netbios
inspect the rsh
inspect the rtsp
inspect the skinny
inspect esmtp
inspect sqlnet
inspect sunrpc
inspect the tftp
inspect the sip
inspect xdmcp
!
global service-policy global_policy
context of prompt hostname
no remote anonymous reporting call
call-home
Profile of CiscoTAC-1
no active account
http https://tools.cisco.com/its/service/oddce/services/De destination address
email address of destination [email protected] / * /
destination-mode http transport
Subscribe to alert-group diagnosis
Subscribe to alert-group environment
Subscribe to alert-group monthly periodic inventory
monthly periodicals to subscribe to alert-group configuration
daily periodic subscribe to alert-group telemetry
Cryptochecksum:80003da27b3641b2123e30df5ef6b320
: end
cvpn #.

Hello

You must ensure that networks l3 behind firewalls have itinerary for your "VPNpool" subnet and you need create the rule of no - NAT as shown below

NAT (inside) 0 access-list SHEEP

HTH

Averroès.

Cannot ping hosts on the same vlan on the 2 switches.

Hey guys so I create my own network in Packet Tracer 6.3. While the hosts can ping others on the same switch 2960 and VLAN, they are unable to ping a host on another switch in the same VLAN. For example. Josh PC on S1 (192.168.10.10) cannot ping PC Doge on S2 (192.168.10.13). I'm sure that they are on the same subnet, so I thing it is a problem of junction...

S1:

S1 #show ip int br

Interface IP-Address OK? Method State Protocol

FastEthernet0/1 unassigned YES manual up up

FastEthernet0/2 unassigned YES manual up up

FastEthernet0/3 unassigned YES manual up up

FastEthernet0/4 unassigned YES manual up up

FastEthernet0/5 unassigned YES manual administratively down down

FastEthernet0/6 unassigned YES manual administratively down down

FastEthernet0/7 unassigned YES manual administratively down down

FastEthernet0/8 unassigned YES manual administratively down down

FastEthernet0/9 unassigned YES manual administratively down down

FastEthernet0/10 unassigned YES manual administratively down down

FastEthernet0/11 unassigned YES manual administratively down down

FastEthernet0/12 unassigned YES manual administratively down down

FastEthernet0/13 unassigned YES manual administratively down down

FastEthernet0/14 unassigned YES manual administratively down down

FastEthernet0/15 unassigned YES manual administratively down down

FastEthernet0/16 unassigned YES manual administratively down down

FastEthernet0/17 unassigned YES manual administratively down down

FastEthernet0/18 unassigned YES manual administratively down down

FastEthernet0/19 unassigned YES manual administratively down down

FastEthernet0/20 unassigned YES manual administratively down down

FastEthernet0/21 unassigned YES manual administratively down down

FastEthernet0/22 unassigned YES manual administratively down down

FastEthernet0/23 unassigned YES manual administratively down down

FastEthernet0/24 unassigned YES manual administratively down down

GigabitEthernet0/1 unassigned YES manual down down

GigabitEthernet0/2 unassigned YES manual down down

Vlan1 unassigned YES manual administratively down down

Vlan2 unassigned YES manual downwards upwards

Vlan10 unassigned YES manual up up

S1 #show interface f0/1 switchport

Name: Fa0/1

Switchport: enabled

Administrative mode: trunk

Operational mode: trunk

Encapsulation of administrative circuits: dot1q

Operational Trunking encapsulation: dot1q

Trunking negotiation: Off

The VIRTUAL LAN access mode: (default) 1

Native mode VLAN Trunking: 2 (native)

The voice of VLAN: no

Private-vlan host association Directors: no

Mapping of private - vlan management: no

Private-vlan trunk administration VLAN native: no

Private - vlan administration trunk encapsulation: dot1q

Private-vlan trunk administration VLAN normal: no

Private-vlan trunk administration private VLAN: no

Private-vlan operational: no

VLAN Trunking enabled: ALL

Pruning VLANS enabled: 2-1001

Capture Mode disabled

Capture VLAN allowed: ALL

Protected: false

The unit trust: no

S1 #show vlan br

Ports of status for the name of VLAN

---- -------------------------------- --------- -------------------------------

1 by default active Fa0/5, Fa0/6, Fa0/7, Fa0/8

Fa0/9, Fa0/10, Fa0/11, Fa0/12

FA0/13, Fa0/14, Fa0/15, Fa0/16

FA0/17, Fa0/18, Fa0/19, Fa0/20

FA0/21, Fa0/22, Fa0/23 and Fa0/24

Gig0/1, Gig0/2

2 active native

5 active

10 active VLAN0010 Fa0/2, Fa0/3, Fa0/4

active by default fddi 1002

assets of token-ring-default 1003

1004 fddinet - default active

1005 trnet - default active

Trunk interface #show S1

VLAN Mode Encapsulation native port State

FA0/1 on 802. 1 trunking q 2

Port VLAN allowed on trunk

5,10,20 FA0/1

Port VLAN authorized and active in the field of management

FA0/1 5,10

VLAN port extending on transmission State and no tree pruned

FA0/1 5,10

S1 #show mac-address-table

Mac address table

-------------------------------------------

VLAN Mac Address Type Ports

---- ----------- -------- -----

5 00d0.d37a.ed01 DYNAMICS Fa0/1

S2:

S2 #show ip int br

Interface IP-Address OK? Method State Protocol

FastEthernet0/1 unassigned YES manual up up

FastEthernet0/2 unassigned YES manual up up

FastEthernet0/3 unassigned YES manual up up

FastEthernet0/4 unassigned YES manual up up

FastEthernet0/5 unassigned YES manual administratively down down

FastEthernet0/6 unassigned YES manual administratively down down

FastEthernet0/7 unassigned YES manual administratively down down

FastEthernet0/8 unassigned YES manual administratively down down

FastEthernet0/9 unassigned YES manual administratively down down

FastEthernet0/10 unassigned YES manual administratively down down

FastEthernet0/11 unassigned YES manual administratively down down

FastEthernet0/12 unassigned YES manual administratively down down

FastEthernet0/13 unassigned YES manual administratively down down

FastEthernet0/14 unassigned YES manual administratively down down

FastEthernet0/15 unassigned YES manual administratively down down

FastEthernet0/16 unassigned YES manual administratively down down

FastEthernet0/17 unassigned YES manual administratively down down

FastEthernet0/18 unassigned YES manual administratively down down

FastEthernet0/19 unassigned YES manual administratively down down

FastEthernet0/20 unassigned YES manual administratively down down

FastEthernet0/21 unassigned YES manual administratively down down

FastEthernet0/22 unassigned YES manual administratively down down

FastEthernet0/23 unassigned YES manual administratively down down

FastEthernet0/24 unassigned YES manual administratively down down

GigabitEthernet0/1 unassigned YES manual down down

GigabitEthernet0/2 unassigned YES manual down down

Vlan1 unassigned YES manual administratively down down

Vlan2 unassigned YES manual downwards upwards

Vlan5 unassigned YES manual up up

Vlan10 unassigned YES manual up up

Vlan20 unassigned YES manual up up

Vlan99 unassigned YES manual administratively down down

S2 #show interface f0/1 switchport

Name: Fa0/1

Switchport: enabled

Administrative mode: trunk

Operational mode: trunk

Encapsulation of administrative circuits: dot1q

Operational Trunking encapsulation: dot1q

Trunking negotiation: on

The VIRTUAL LAN access mode: (default) 1

Native mode VLAN Trunking: 2 (native)

The voice of VLAN: no

Private-vlan host association Directors: no

Mapping of private - vlan management: no

Private-vlan trunk administration VLAN native: no

Private - vlan administration trunk encapsulation: dot1q

Private-vlan trunk administration VLAN normal: no

Private-vlan trunk administration private VLAN: no

Private-vlan operational: no

VLAN Trunking enabled: ALL

Pruning VLANS enabled: 2-1001

Capture Mode disabled

Capture VLAN allowed: ALL

Protected: false

The unit trust: no

S2 #show vlan br

Ports of status for the name of VLAN

---- -------------------------------- --------- -------------------------------

1 by default active Fa0/5, Fa0/6, Fa0/7, Fa0/8

Fa0/9, Fa0/10, Fa0/11, Fa0/12

FA0/13, Fa0/14, Fa0/15, Fa0/16

FA0/17, Fa0/18, Fa0/19, Fa0/20

FA0/21, Fa0/22, Fa0/23 and Fa0/24

Gig0/1, Gig0/2

2 active native

5 active

10 VLAN0010 active Fa0/4

20 VLAN0020 active Fa0/2, Fa0/3

active by default fddi 1002

assets of token-ring-default 1003

1004 fddinet - default active

1005 trnet - default active

S2 #show mac-address-table

Mac address table

-------------------------------------------

VLAN Mac Address Type Ports

---- ----------- -------- -----

2 0030.f2c1.94e5 STATIC Fa0/1

2 0060.5c83.3401 STATIC Fa0/1

10 0002.4ae9.6964 STATIC Fa0/4

10 0060.5c83.3401 STATIC Fa0/1

20 0009.7c9a.a134 STATIC Fa0/2

----------------------------------------------------------------------------------

Let me know what I missed here. All connections are made with a straight through cable.

See you soon

Josh

Try to remove the S2 switchport port-security:
```
interface FastEthernet0/1
 no switchport port-security
```

The VPN Clients cannot Ping hosts

I'll include a post my config. I have clients that connect through the VPN tunnel on the 180.0.0.0/24 network, 192.168.1.0/24 is the main network for the office.

I can connect to the VPN, and I received a correct address assignment. I belive tunneling can be configured correctly in the aspect that I can always connect to the internet then on the VPN, but I can't ping all hosts on the 192.168.1.0 network. In the journal of the ASDM debugging, I see pings to the ASA, but no response is received on the client.

February 21, 2013

21:54:26

180.0.0.1

53508

192.168.1.1

Built of ICMP incoming connections for faddr gaddr laddr 192.168.1.1/0 (christopher) 192.168.1.1/0 180.0.0.1/53508

Any help would be greatly appreciated, I'm currently presuring my CCNP so I would get a deeper understanding of how to resolve these issues.

-Chris

hostname RegencyRE - ASA

domain regencyrealestate.info

activate 2/VA7dRFkv6fjd1X of encrypted password

2KFQnbNIdI.2KYOU encrypted passwd

names of

name 180.0.0.0 Regency

interface Ethernet0/0

switchport access vlan 2

interface Ethernet0/1

link to the description of REGENCYSERVER

interface Ethernet0/2

interface Ethernet0/3

interface Ethernet0/4

interface Ethernet0/5

interface Ethernet0/6

interface Ethernet0/7

link to the description of RegencyRE-AP

interface Vlan1

nameif inside

security-level 100

192.168.1.120 IP address 255.255.255.0

interface Vlan2

nameif outside

security-level 0

IP x.x.x.x 255.255.255.248

passive FTP mode

clock timezone PST - 8

clock summer-time recurring PDT

DNS lookup field inside

DNS domain-lookup outside

DNS server-group DefaultDNS

Server name 208.67.220.220

name-server 208.67.222.222

domain regencyrealestate.info

inside_nat0_outbound to access ip 192.168.1.0 scope list allow 255.255.255.0 Regency 255.255.255.224

RegencyRE_splitTunnelAcl list standard access allowed 192.168.1.0 255.255.255.0

outside_access_in list extended access permit icmp any one

pager lines 24

Enable logging

asdm of logging of information

Within 1500 MTU

Outside 1500 MTU

mask Regency 180.0.0.1 - 180.0.0.20 255.255.255.0 IP local pool

ICMP unreachable rate-limit 1 burst-size 1

ICMP allow any inside

ICMP allow all outside

ASDM 255.255.255.0 inside Regency location

ASDM location 192.168.0.0 255.255.0.0 inside

don't allow no asdm history

ARP timeout 14400

Global 1 interface (outside)

NAT (inside) 0-list of access inside_nat0_outbound

Access-group outside_access_in in interface outside

Route outside 0.0.0.0 0.0.0.0 12.186.110.2 1

Route inside 192.0.0.0 255.0.0.0 192.168.1.102 1

Timeout xlate 03:00

Timeout conn 01:00 half-closed 0:10:00 udp 0:02:00 icmp 0:00:02

Sunrpc timeout 0:10:00 h323 0:05:00 h225 mgcp from 01:00 0:05:00 mgcp-pat 0:05:00

Sip timeout 0:30:00 sip_media 0:02:00 prompt Protocol sip-0: 03:00 sip - disconnect 0:02:00

Timeout sip-provisional-media 0:02:00 uauth 0:05:00 absolute

timeout tcp-proxy-reassembly 0:01:00

Floating conn timeout 0:00:00

dynamic-access-policy-registration DfltAccessPolicy

the ssh LOCAL console AAA authentication

LOCAL AAA authentication serial console

http server enable 8443

http 0.0.0.0 0.0.0.0 outdoors

http 0.0.0.0 255.255.255.0 inside

No snmp server location

No snmp Server contact

Server enable SNMP traps snmp authentication linkup, linkdown cold start

Crypto ipsec transform-set ESP-AES-256-MD5 esp-aes-256 esp-md5-hmac

Crypto ipsec transform-set ESP-DES-SHA esp - esp-sha-hmac

Crypto ipsec transform-set ESP-DES-MD5 esp - esp-md5-hmac

Crypto ipsec transform-set ESP-AES-192-MD5 esp-aes-192 esp-md5-hmac

Crypto ipsec transform-set ESP-3DES-MD5-esp-3des esp-md5-hmac

Crypto ipsec transform-set ESP-AES-256-SHA 256 - aes - esp esp-sha-hmac

Crypto ipsec transform-set ESP-AES-128-SHA aes - esp esp-sha-hmac

Crypto ipsec transform-set ESP-AES-192-SHA esp-aes-192 esp-sha-hmac

Crypto ipsec transform-set ESP-AES-128-MD5-esp - aes esp-md5-hmac

Crypto ipsec transform-set esp-SHA-ESP-3DES-3des esp-sha-hmac

life crypto ipsec security association seconds 28800

Crypto ipsec kilobytes of life - safety 4608000 association

crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 pfs Group1 set

Crypto dynamic-map SYSTEM_DEFAULT_CRYPTO_MAP 65535 value transform-set ESP-AES-128-SHA ESP-AES-128-MD5 ESP-AES-192-SHA ESP-AES-192-MD5 ESP-AES-256-SHA ESP-AES-256-MD5 ESP-3DES-SHA MD5-ESP-3DES ESP-DES-SHA ESP-DES-MD5

outside_map card crypto 65535-isakmp dynamic ipsec SYSTEM_DEFAULT_CRYPTO_MAP

outside_map interface card crypto outside

crypto ISAKMP allow outside

crypto ISAKMP policy 10

preshared authentication

3des encryption

sha hash

Group 2

life 86400

Telnet timeout 5

SSH 0.0.0.0 0.0.0.0 inside

SSH 0.0.0.0 0.0.0.0 outdoors

SSH timeout 15

SSH version 2

Console timeout 0

dhcprelay Server 192.168.1.102 inside

a basic threat threat detection

Statistics-list of access threat detection

no statistical threat detection tcp-interception

NTP server 69.25.96.13 prefer external source

NTP server 216.171.124.36 prefer external source

WebVPN

internal RegencyRE group strategy

attributes of Group Policy RegencyRE

value of server DNS 208.67.220.220 208.67.222.222

Protocol-tunnel-VPN IPSec

Split-tunnel-policy tunnelspecified

value of Split-tunnel-network-list RegencyRE_splitTunnelAcl

username password encrypted adriana privilege 0

christopher encrypted privilege 15 password username

irene encrypted password privilege 0 username

type tunnel-group RegencyRE remote access

attributes global-tunnel-group RegencyRE

Regency address pool

Group Policy - by default-RegencyRE

IPSec-attributes tunnel-group RegencyRE

pre-shared key R3 & eNcY1.

class-map inspection_default

match default-inspection-traffic

type of policy-card inspect dns preset_dns_map

parameters

maximum message length automatic of customer

message-length maximum 512

Policy-map global_policy

class inspection_default

inspect the preset_dns_map dns

inspect the ftp

inspect h323 h225

inspect the h323 ras

Review the ip options

inspect the netbios

inspect the rsh

inspect the rtsp

inspect the skinny

inspect esmtp

inspect sqlnet

inspect sunrpc

inspect the tftp

inspect the sip

inspect xdmcp

global service-policy global_policy

context of prompt hostname

no remote anonymous reporting call

call-home

Profile of CiscoTAC-1

no active account

http https://tools.cisco.com/its/service/oddce/services/DDCEService destination address

email address of destination [email protected] / * /

destination-mode http transport

Subscribe to alert-group diagnosis

Subscribe to alert-group environment

Subscribe to alert-group monthly periodic inventory

monthly periodicals to subscribe to alert-group configuration

daily periodic subscribe to alert-group telemetry

Cryptochecksum:35bc3a41701f7f8e9dde5fa35532896d

: end

Hello

-be sure that the destination host 192.168.1.x has a route towards 180.0.0.0 by the ASA gateway.

-Configure the following figure:

capture capin interface inside match icmp 192.168.1.x host 180.0.0.x

capture ASP asp type - drop all

then make a continuous ping and get 'show capin cap' and 'asp cap.

-then check the ping, the 'encrypted' counter is increasing in the VPN client statistics

I would like to know about it, hope this helps

----

Mashal

Cannot ping host VMWARE

If lost the connection to one of my VMware vCenter servers.
I can still do the following...
- use the vSphere client to go directly to it.
- Ping the servers running on it.
I think I broke one of the VMKernel ports or its delivery. This would be the case?
What should I change to get this working? I know it's a gateway or a routing problem but can not see what is wrong.
In my view, the line I marked / highlighted must really point to 192.168.101.1. Is it possible to change this gateway "Local subnet" or have I got it all wrong.
Any guidance would be greatly appreciated.

Problem was with the vswitch for her ip and gateway.

Cannot ping via the VPN client host when static NAT translations are used

Hello, I have a SRI 3825 configured for Cisco VPN client access.

There are also several hosts on the internal network of the static NAT translations have a services facing outwards.

Everything works as expected with the exception that I cannot ping hosts on the internal network once connected via VPN client that is internal IP addresses have the static NAT translations in external public addresses, I ping any host that does not have static NAT translation.

For example, in the example below, I cannot ping 192.168.1.1 and 192.168.1.2, but I can ping to the internal interface of the router, and any other host on the LAN, I can ping all hosts in the router itself.

Any help would be appreciated.

Concerning

!

session of crypto consignment

!

crypto ISAKMP policy 10

BA 3des

preshared authentication

Group 2

!

ISAKMP crypto client configuration group vpnclient

key S3Cu4Ke!

DNS 192.168.1.1 192.168.1.2

domain domain.com

pool dhcppool

ACL 198

Save-password

PFS

netmask 255.255.255.0

!

!

Crypto ipsec transform-set-SECURE 3DES esp-3des esp-sha-hmac

!

Crypto-map dynamic dynmap 10

86400 seconds, life of security association set

game of transformation-3DES-SECURE

market arriere-route

!

card crypto client cryptomap of authentication list drauthen

card crypto isakmp authorization list drauthor cryptomap

client configuration address card crypto cryptomap answer

map cryptomap 65535-isakmp ipsec crypto dynamic dynmap

!

interface GigabitEthernet0/0

NAT outside IP

IP 1.2.3.4 255.255.255.240

cryptomap card crypto

!

interface GigabitEthernet0/1

IP 192.168.1.254 255.255.255.0

IP nat inside

!

IP local pool dhcppool 192.168.2.50 192.168.2.100

!

Note access-list 198 * Split Tunnel encrypted traffic *.
access-list 198 allow ip 192.168.1.0 0.0.0.255 192.168.2.0 0.0.0.255

!
Note access-list 199 * NAT0 ACL *.
access-list 199 deny ip 192.168.0.0 0.0.255.255 192.168.0.0 0.0.255.255
access-list 199 permit ip 192.168.1.0 0.0.0.255 any

!

Sheep allowed 10 route map
corresponds to the IP 199

!
IP nat inside source map route sheep interface GigabitEthernet0/0 overload

!

IP nat inside source static 192.168.1.1 1.2.3.5
IP nat inside source static 192.168.1.2 1.2.3.6

The problem seems to be that static NAT take your nat exemption.

The solution would be:

IP nat inside source static 192.168.1.1 1.2.3.5 sheep map route
IP nat inside source static 192.168.1.2 1.2.3.6 sheep map route

HTH

Herbert

ACI - cannot reach hosts outside the fabric until the traffic is inititated from a host outside in a host connected to the fabric

I have a group of the same EPG and VLAN statically mapped ports on my fabric of ACI. One port connects to a port on a stack of 3750 x uplink. Hosts on the fabric, I cannot ping hosts on the 3750 until I have initiated traffic from hosts on the 3750 in the fabric. Once it done on each host of 3750, they can talk to each other. Why is this happening?

Thank you!

When traffic is a failure, the destination will probably not learned as an EP in the fabric. You can check by looking at the operational tab of the EPG.

Once you ping the 3750, we learn the EP and traffic works from the original source. When the BD "Equipment Proxy" mode, the destination must be learned.

If you change the mode of the 'Flood' comic, then inundate us and learn as a normal switch.

Joey

Comments and host OS can ping each other; but all the other hosts on the same subnet cannot ping guest OS

I use Bridge network. I tried to delete and recreate the NIC (did not help). I've upgraded to the latest version of VMware Server (20.0.0 build 122589) with the same result. Stub here. Anyone have any ideas? Thank you.

What is your host and guest operating system? Are WHAT NIC configured correctly (IP, DNS, gateway, etc.).

Are all necessary ports (firewall, antyvir)?

J.

Difficulty ping between the hosts and guests

Hello
I want to establish network connectivity between my host OS (XPsp3) and my guests (CentOS5.5 and Windows 7).
So far, I can ping between guests, but not between host and guest, or comments to the host. When I try, I get a message "destination host unreachable".
When I configured my virtual machines in a first time, I put them to 'Host-Only' and I need to keep it like that for the purpose of what I do with them - which is the problem?
Ipconfig and ifconfig outs of machines attached.
Bests
Adam

... If you use VMware Workstation, you could also reconfigure VMnet1 in the 192.168. 8.x subnet using the "Virtual Network Editor"

André

The host cannot ping

Hello
I can't reach my host. What could be the problem?
I am using Vmware Server 2.0.1 Build 156745
Host: Windows XP Professional sp2
IP:192.168.146.1 host (vmnet1)
Hardware: Computer laptop Dell 630
Comments: Linux
CentOS 2.16.0
GuestIP:192.168.146.120
Comments cannot ping the host
Host cannot ping the prompt
I tried to configure the nat and the host only to connect. Nat could also be able to reach the external pages.
I appreciate any ideas

Is the fixed prompt on DHCP or IP?

What network cards do you have on the host and bridged (vmnetcfg.exe run as administrator)?

Is the physical card on the guest living/connected - sometimes to the life of a card NETWORK disconnected will no connectivity in the guest?

Have you recently changed the VMware network in the host? If so, you will need to restart the VMware services or reboot the host.

Is there a firewall clutter it?

Is the card NETWORK connected to the prompt - it shouldn't be a red cross on the network icon in the list of the material in the center of the console pane when the virtual machine is selected in the left pane?

The MAC address or virtual and physical adapters in the host and the single guest, that is not duplicated?

If all this pans, can be helpful to remove the NETWORK card in the prompt and add a. Also, what type of NETWORK adapter is it in the guest - 'flexible' or 'e1000 '? Should be 'flexible' for Linux - post (tie) the .vmx doubt customers.

--

If you have found this device or any other answer useful please consider the use of buttons useful or Correct to award points.

Cannot ping the Virtual Machine by host

Hi all,
Please help, I use VMWare Workstation 6.5 and I have a physical operating system which is Windows XP SP2, I have a network card, but not connected to a physical switch, the IP address is 192.168.0.1. I installed a Virtual Machine using Microsoft Windows 2003 server as the operating system, promote as domain controller, install the DHCP, DNS service and assign an IP 192.168.0.2, no default gateway.
My VMnet1 on physical operating system has an IP 192.168.204.1 and VMNet8 has an IP 192.168.126.1.
The host, I cannot ping the 192.168.0.2 which is the IP address of the Virtual Machine. Even in the Virtual Machine, I can not ping 192.168.0.1 is the IP address of the host. From what I read, the physical and the virtual machine were connected with a virtual switch. Am I wrong?
Any advice?
Thanks in advance.

They SEEM to be in different networks, you need search routing between them,... since they differnet networks...

on the other

they do host and the virtual machine on the same subnet / network for EXAMPLE: class C class network 192.168.200.0/24

granting of points if my answer was helpful... Thank you > > > > > > > >

concerning

Joe

Cannot ping the host name of the operating system in vmware after intall kaspersky antivirus 2009

Dear all
I use windows xp professional, and XP, I use vmware workstation 6.0.2 I installed RHEL4 in vmware.
I was able to ping the host name of the guest operating system after you have entered the information (192.168.1.2 appserver.ibcs appserver)
in the C:\WINDOWS\system32\drivers\etc\hosts file. But after installing Kaspersky Antivirus 2009, I couldn't ping to the
Comments more bones by host name. But if I remove kaspersky anti-virus it pings again.
............ Can someone give me any solution please

Check your firewall Karspersky rules. Set the IP of comments as a secure IP.

Concerning

Cannot ping a virtual machine, except on the host computer.

I have a host of SuSE, built on a chassis of IBM. It has a link for the failover interface. It has an IP of 10.10.138.196. SM 255.255.255.128. DG 10.10.138.129. I can ping this machine without problem. On that note, I have a virtual machine of SuSE. It has the same mask and gateway with an IP address of 10.10.138.197. It can ping the host (196) and the host can it ping. However, he cannot ping to the gateway by defaut.129. He receives a message Impossible to its own virtual interface. I have installation bridged networking early with no luck.
I tried to change the DG on the guest a.196. I have installation routes by default, and specific directions to 10.10.138.129 on the host and the guest without success. I talked to a few colleagues and they are not of course either. I need this available, so it can be used for a variety of applications.

You will not see a virtual NETWORK adapter for bridged interface, only for NAT and the host-only networking. There will be a device/dev/vmnet0, but that is not actually used to fill itself.

Your problem is that your bridged interface is bound to the wrong card on the host: it must be related to "bond0" not "eth0". You will need to re - run /usr/bin/vmware-config.pl to address which forces all running VMs to be stopped.

---

If you have found this device or any other answer useful please consider the use of buttons useful or Correct to award points.

cannot ping external hosts to site 2 site vpn

Hi all

I have 2 sites configured as VPN L2L back to my ASA5520. a site uses a PIX525 and the other an ASA5505. I can access all the resources on my netwrok private without a problem and all traffic from remote sites is "protected". the issue I'm having is that I can not ping and external guests. for example, if I try to ping 4.2.2.1 emanating from a host on a remote site it times out. I can ping no matter what resource a my networks 'private' to any site without problem. any suggestions? Thank you.

If you are relying on access to Internet through the tunnel L2L (because you're tunnel everything), then you need to...

(1) configure uturn and outside nat for the remote network on the ASA station so traffic can leave the same interface it came with a public IP address for the Internet:

NAT (outside) 99

Global interface 99 (external)

permit same-security-traffic intra-interface

Or

(2) put in place a tunnel default gateway pointing to an internal router which has access to the internet

Route inside 0.0.0.0 0.0.0.0 in tunnel

-heather

Cannot ping host or guest using VM Workstation 5.5

Similar Questions

Maybe you are looking for