I did put in the command you suggested utils service list . but the screen scroll fast and I can not see what was displayed except the last out put. is there a command to put in after  utils service list command to display partial line

by the way put in the https://192.168.1.2/ccmadmin  did not get me anyware.

Thanks

utils service list page

Hit enter to scroll one page at a time.

Either Tomcat hasn't started, your network connection is busted, or your server is hung after VMWare load (seen it before). Test 1 and 2 first, if necessary - reboot the VM Machine.

here is what I did .

admin : ping 192.168.1.2 --> not valid command

admin : utils service  ping 192.168.1.2--> not valid command

show utils service page --> Tomcat { started }

utils system restart --> restart the system .. still not go.. any other suggestions please.

Thanks

The command for pinging is: utils network ping

for instance: utils network ping 192.168.1.1

Regards,

Bill

Have you checked/modified the vmware/vmnet config as I suggested?  Just curious.  I think there could be something going on there.

Maybe if you could give us some of the finer points on your vmware setup that would be swell.

HTH.

Regards,
Bill

None of those are valid commands, bro. You can use the ? just like IOS to see what are/are not valid commands. Use the utils network ping x.x.x.x (whatever address you want). We've got plenty of suggestions, but you need rule out the basics that we've pointed out first before it's worth moving on.

Hailey

You can use the command: utils service list page

What Hailey is getting at is that you need to check the services to see if the Cisco Tomcat service is running. If it isn't, then you won't have a web page to get to. After a fresh install it takes a little time for the Tomcat to accept connections. Given the time elapsed since the OP, I don't think that is pertinent. However, if you see services in a "Starting" state then that could indicate your network configuration could use some attention.

On a re-read of the original post (OP) I see that I missed an obvious area to check: vmware/vmnet configs.

Your guest is on VMNet8 if I follow your OP. This is used for NAT'ng clients. I am going to guess that the station you are trying to use to connect to this host is the workstation running vmware. Is that correct? Are you trying to use VMNet8 to NAT the connection from your CUCM to your lab/testbed. I don't use this VMNet myself. I typically create a new VM network (e.g. VMNet2) in the vmware application. I bind it to one of my real network interfaces. If this is vmware workstation and the client you are trying to connect with is the vmware host, then I would also add a secondary address on the physical LAN interface (e.g. 192.168.1.250/24). This would be the LAN interface associated to VMNet2 (for example). Essentially putting your PC on the same IP netork as the CUCM host.

Lastly, check your PC-based firewall. It does get involved in this network communication.

HTH.

Regards,

Bill

Please remember to rate helpful posts.

Thank you ..

I am new to Vmware as well as cucm.

what I have is hp dl360 I installed window server 2000. and the VMware is on the same machine . when I log in to the console I choose local.

do you thing I should change my network setting and if yes how to do that . your help is very much appreciated

Well, it would be in your best interest to read up a bit on the version of VMWare you're using as there are many flavors. Bill and I use one flavor but there are many others. You also need to get familiar with the CLI troubleshooting commands - by reading up first. Aside from that, I don't recommend VMWare DHCP or NAT. I bind my "lab" interface to a specific NIC on my server. I can't tell you specifically how to do that because you may be running a different version of VM than we are.

Well, I would recommend getting comfortable with the vmware docs for your version of software. Most likely vmware workstation or vmware server. Here are some links to get you jump started:

Here is something on vmware 5.x workstations. Somewhat dated but may be helpful:

http://www.vmware.com/support/ws5/doc/ws_net_configurations_changing_bridged_windows.html

admin guide for vmware server 2.x: http://www.vmware.com/pdf/vmserver2.pdf

vmware community site. Like a netpro for vmware: http://communities.vmware.com/home.jspa

Changing the network settings is pretty easy. Just search for "changing vmware network" in google and you will find what you need.

And, yes, I recommend changing the vmnet because vmnet8 isn't what you are looking to use.

HTH.

Regards,

Bill

Please remember to rate helpful posts.

I was able to ping 192.168.1.2 witch is the ip I gave to my interface. but I am not able to ping the gtwy that I assigned 192.168.1.1

I am not able to ping 192.168.0.1 for VmNET1

I am not able to ping 192.168.60.1 for VmNET 8

Not surprising. You need to take a moment and read up on the vmware vmnet. Try to assign a different vmnet then vmnet8 and give that a go. I just sent you a bunch of links to check.

HTH.

Regards,

Bill