Joseph Mack PhD, High Performance Computing & Scientific Visualisation LMIT, Supporting the EPA Research Triangle Park, NC 919-541-0007 Federal Infrastructure Contact-Ravi Nair 919-541-5467 - [EMAIL PROTECTED], Federal Visualization Contact - Joe Retzer, Ph.D. 919-541-4190 - [EMAIL PROTECTED]
[EMAIL PROTECTED] wrote on 04/13/2005 05:02:44 PM: > One of the tests you can always do is > > dx -uionly & > dx -execonly didn't know how to do this, thanks Well it works now, both this way and by just firing up dx the normal way. The only difference I noticed was that I did it early this morning when no-one was on the network and the various dx windows came up quickly. The machine is at the other end of the universe and yesterday afternoon it was taking about 20secs to bring up xclock and about a minute to bring up the various dx windows). Yesterday I was getting timeouts connecting to the dx server. I had assumed that no matter how slow the network was to my display that the client and server at the other end would not be affected, both being on the same machine. Are they waiting for the various dx windows to come up at my end first? After I showed myself that it's working, I called up the user at the other end and he can bring up dx just fine, so I'll assume the problem is handled. Thanks for the help Joe > Then go into the UI and try to connect to an already > running server. > See if it allows you to get past it. If not, then I'd > almost bet that > there is some kind of network problem on the machine (sockets are > somehow getting blocked). > > David > > -- > ............................................................................. > David L. Thompson Visualization and > Imagery Solutions, Inc. > mailto:[EMAIL PROTECTED] 5515 Skyway Drive, > Missoula, MT 59804 > Phone : (406)756-7472
