On Monday 04 November 2002 04:54, Moore, Paul wrote:
From: Moore, Paul
Looks like it thinks it's being asked to open a display on a machine called "oem". That's very weird, as my machine isn't called "oem".
"oem" usually stands for "Original Equipment Manufacturer" -- for instance, when you buy a "dell" computer, it may come with a hard drive built for IBM; IBM in turn sells the drive to DELL at an "OEM" price, DELL in turn marks it on an invoice as an "IBM hard drive" [at retail prices]
Oh, poo. It looks like it may be related to DNS.
[...snipped finger-pointing example]
I can work around this temporarily by putting my PC name into the Linux box's /etc/hosts file, which fixes the resolution, but as my PC is on DHCP, that only works until I get a new IP address assigned :-( [...] but can anyone suggest any other possible workarounds for a severely broken DNS?
While I don't have a ready example program or script, I do have a suggestion (hopefully someone can turn the suggestion into a workable example) My suggestion is to dynamicallly update your /etc/hosts file as part of your ifup script (oh, wait, this is the windows machine we're talking about, right? Is there an equivalient process to "ifup" under windows?) In DOS, the command "ipconfig" shows you your current IP address, etc. Perhaps as part of your AUTOEXEC.BAT file you can run IPCONFIG and parse the output [I would presume "right after logging in" you would have ready access to the current IP number, and perhaps some idea of how long the "lease" is valid] You could then shoot this over to the linux system via any convenient means [i.e., telnet, smtp, or even http using a simple CGI script/form] The linux system could then update /etc/hosts (after ensuring the "data" received is *just* an ip number and not some funky buffer-overrun attempt -- you'd be surprised at who, how, and where people will try to hack systems...)