| Re: socket problems.. Desperate! [message #25406] |
Fri, 08 June 2001 12:45 |
Brad Gom
Messages: 49
Registered: August 1997
|
Member |
|
|
ooh- thanks for the speedy replies. what a great newsgroup.
Craig Markwardt wrote:
>
> This looks like a name server problem. Are the DNS settings the same
> between machines? The strange thing is that the hostname you gave is
> an IP number already...
>
Thats the thing I don't understand. Here's the weirder part: I just tried
opening an IDL socket using
the real hostname (blahblah.physics.uleth.ca) and this works. I thought that
it would choke for sure when given the hostname rather than IP.
So it looks like I have a workaround, but I don't think I'm any wiser.
Thanks
Brad Gom
-
Attachment: brad.gom.vcf
(Size: 0.31KB, Downloaded 81 times)
|
|
|
|
| Re: socket problems.. Desperate! [message #25408 is a reply to message #25406] |
Fri, 08 June 2001 11:29  |
Pavel A. Romashkin
Messages: 531
Registered: November 2000
|
Senior Member |
|
|
Oh boy, doesn't this sound like a registry hacking time :-(
MS web site has a fairly detailed description of their TCP/IP related
registry entries. Try to compare them on both machines. Check the IDL
related entries, there shouldn't be too many. But I'd back the
registiries up first.
Cheers,
Pavel
Brad Gom wrote:
>
> Hi all,
>
> I have a rather pressing problem with IDL sockets: I have written an
> IDL application that uses a socket to talk to a RTLinux box to control
> an instrument and gather data from it for analysis. The system works
> fine on my windows PCs, but I've just tested it on the laptop that will
> actually control the experiment and I get the following error from IDL
> SOCKET:
>
> SOCKET: Unable to lookup host. Unit 101, File: 142.66.41.72
>
> I can telnet and ping the 142.66.41.72 machine from the laptop and it
> works fine, but the IDL socket routine fails. As I mentioned, the socket
> works from the other PCs in my lab, so this is probably a windows
> problem on the laptop - So I need to know what this message means so I
> can figure out what to change in my windows settings!
>
> Does anyone have any insight as to what might cause this type of error?
> -hopefully before next week when this instrument has observing time one
> of the largest telescopes :)t
|
|
|
|
| Re: socket problems.. Desperate! [message #25410 is a reply to message #25408] |
Fri, 08 June 2001 11:12 |
Craig Markwardt
Messages: 1869
Registered: November 1996
|
Senior Member |
|
|
Brad Gom <brad.gom@uleth.ca> writes:
> SOCKET: Unable to lookup host. Unit 101, File: 142.66.41.72
...
> Does anyone have any insight as to what might cause this type of error?
> -hopefully before next week when this instrument has observing time one
> of the largest telescopes :)
This looks like a name server problem. Are the DNS settings the same
between machines? The strange thing is that the hostname you gave is
an IP number already...
Perhaps you could add a local host entry like this?
142.66.41.72 142.66.41.72
Craig
--
------------------------------------------------------------ --------------
Craig B. Markwardt, Ph.D. EMAIL: craigmnet@cow.physics.wisc.edu
Astrophysics, IDL, Finance, Derivatives | Remove "net" for better response
------------------------------------------------------------ --------------
|
|
|
|
comp.lang.idl-pvwave archive
Members
Search
Help
Login
Home
