If you're using an IP address rather than a hostname, then all we are doing is a straight socket() call to open the socket. If you are specifying a hostname then we do a gethostbyname() and then the socket() call.
Given NETBIOS over TCP/IP works, it's entirely possible that a gethostbyname() may actually try to do a WINS resolution. However, I'm not an expert on that area of windows.
If you have it enabled, can you try disabling the WINS name resolution on your system(s) and see if that improves things?
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Anonymous
-
2004-09-17
Problem was: on the 'slow' machines there was a VM ware connection running.
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Do you have VMWare connections running like the person who originally initiated this forum posting? He had posted to say that was the reason on his machines.
Is the response time for a regular (non-STAF) ping long as well?
You may need to track down the TCP issues in your network or in the configuration of TCP on your Windows machines.
Are there many bridges/firewalls, etc. between the two machines that are taking a while to respond?
Are you pinging by hostname or IP address?
For example, we can do 10 STAF pings from one Windows XP machine to another Windows XP machine (in the same lab) in about 7 seconds.
I am getting the long ping result also, and I am running pings from a Windows XP host to a Linux VM under VMware.
I'll see if I can find out what in my network config causes this - I am running the VM on a host-only network, so I would not have thought that would cause routing problems. I'll let you know what I find out.
David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
As it turns out, my case was simple - my Windows XP host turned on the Windows Firewall for vmnet1 & vmnet8. I turned the firewall off for those two interfaces, and ping time is now as quick as I would expect.
David
If you would like to refer to this comment somewhere else in this project, copy and paste the following link:
Hi
If I use for example the ping command:
staf ipadress ping ping
to some computers in the same network it takes up to more than 5 seconds before i get 'PONG'.
OS: all the computers: XP or windows 2003
STAF: Beta3 (necessary)
Maybe it is dependent on a configuration on the machine I ping to.
What can be the reason and is it possible to fix this and how?
Some help is very welcome! Thanks
Hendrik
Its something to do with NETBIOS, i have done a dump with ethereal and the slow pings are caused by multiple extra NBNS in some way,..., strange.
If you're using an IP address rather than a hostname, then all we are doing is a straight socket() call to open the socket. If you are specifying a hostname then we do a gethostbyname() and then the socket() call.
Given NETBIOS over TCP/IP works, it's entirely possible that a gethostbyname() may actually try to do a WINS resolution. However, I'm not an expert on that area of windows.
If you have it enabled, can you try disabling the WINS name resolution on your system(s) and see if that improves things?
Problem was: on the 'slow' machines there was a VM ware connection running.
Me too facing the same problem.For STAF pinging between machines it takes around 15 seconds.Version of
STAF I am using is v3.1.2 and both clients and server using Windows XP sp2.Can any one provide some help.
Do you have VMWare connections running like the person who originally initiated this forum posting? He had posted to say that was the reason on his machines.
Is the response time for a regular (non-STAF) ping long as well?
You may need to track down the TCP issues in your network or in the configuration of TCP on your Windows machines.
Are there many bridges/firewalls, etc. between the two machines that are taking a while to respond?
Are you pinging by hostname or IP address?
For example, we can do 10 STAF pings from one Windows XP machine to another Windows XP machine (in the same lab) in about 7 seconds.
C:\>STAFLoop
Usage: STAFLoop <# loops> <Where> <Service> <Request>
C:\>STAFLoop 10 client1.mycompany.com ping ping
Total loops: 10
Total time : 7.081
Avg. time : 0.708
Loops/sec : 1.41223
Hi Sharon,
I am getting the long ping result also, and I am running pings from a Windows XP host to a Linux VM under VMware.
I'll see if I can find out what in my network config causes this - I am running the VM on a host-only network, so I would not have thought that would cause routing problems. I'll let you know what I find out.
David
As it turns out, my case was simple - my Windows XP host turned on the Windows Firewall for vmnet1 & vmnet8. I turned the firewall off for those two interfaces, and ping time is now as quick as I would expect.
David