I have an application which has a client edition(workstation) and server edition(service). The client edition is on Windows XP and the server edition is on Windows Server 2003. We have a lot of machines running different setups and networks. The above mentioned client machine application is hanging, only that setup hang-up is there, other than that all of the other systems running on different networks haven't had any issues.
I suspect it will be related to some network issues. Kindly provide the expected network issues which would lead to an application hanging in a client server environment. I have heard that "the same network name identfied with multiple IP addresses which may be causing at least some delays in resolving the names or at worst a failure which will cause a hang," is that correct? Any others?
This is some part of the host file taken from Server. Here the troublesome client machine name is
tvr-lzvrts, but again i can see
lzvrts2, do i need to move this into comments(#). I can see lot of entries without comments
mntis mnefms ht7
188.8.131.52 tvr-lzvrts2 lzvrts2 # TISSON 184.108.40.206 ght7 ht7 # TISSON 220.127.116.11 mns6 mntis mnefms # LEVIS
One more thing, I forgot when I asked about some IP address information, the team said they are using the IP addresses as place holders in the
Hosts file until they have the correct public IP addresses from the customer. The cables are not connected. Do I need to disable these ports until they are ready to use the real IP addresses for the customers?
In the client system, my application takes most of the memory and the CPU usage is around 93%. I confirmed these facts from Task Manager. I can see a lot of flickering going on my application.