At some level Windows must resolve the hostname and find that it is local then try to use something, maybe WINS, to resolve more information about the system, fail on WINS then die completely. This sounds like MS quality at it's finest.
Any idea how configure a samba server to how WINS info so that it will act like a DNS. I will go looking my self. I just don't want to spend a lot of time on WINS if in the end it turns out that is not the fix. Thanks Kin. This could be the answer I was looking for. On Tue, Sep 16, 2008 at 2:10 PM, Kin C Wong <[EMAIL PROTECTED]> wrote: > I thought it was only a couple of computers that needed access - what > about a WINS server. Sorry don't know any specifics. > > > Royce Souther wrote: > > That is an option but modifying over 200 Windows systems any time I > > add or move server is not at the top of my list. > > > > On Tue, Sep 16, 2008 at 1:48 PM, Kin C Wong <[EMAIL PROTECTED] > > <mailto:[EMAIL PROTECTED]>> wrote: > > > > Not an expert on the subject but I believe if you create a lmhosts > > file > > The file should contain something like this: > > > > 102.54.94.91 <http://102.54.94.91> accounting #accounting server > > 102.54.94.94 <http://102.54.94.94> payroll #payroll server > > > > An example of this file can be found at > > c:\windows\system32\drivers\etc > > and is called lmhosts.sam > > > > You should be able to locate the computer by using the associated > name > > rather than the ip address. You will need to do that for each > > computer > > that you want to access these servers. It is a real pain. > > > > > > Royce Souther wrote: > > > I have a school with a few hundred WinXP Pro systems. They are > > all on > > > a Samba domain controlled server for authentication and home > > > directories. It works great except for some reason some names > > will not > > > resolve. I am using IPcop to set hostnames for static systems on > the > > > network. IPcop is the DNS server for the network. If IPcop knows > the > > > name and IP of a local system it will resolve that IP. All the > Linux > > > workstations resolve all names correctly but it seems like Windows > > > will not resolve a hostname unless there is a Samba server > > running on > > > it. That is really stupid and what I would expect from Microsoft > but > > > not helpfull at all. I have servers that privoleged staff need to > > > access from WinXP via Firefox and don't know squat about Windows > > so I > > > would like if someone could help me figure out what is wrong > > with it, > > > all joking aside. > > > > > > As you can see below, *server* can be pinged but the *asterisk* > > server > > > cannot even though nslookup says it can resolve the IP. WTFIUWT! > > Both > > > servers are listed in IPcop. IPcop is at 192.168.0.254 > > <http://192.168.0.254> > > > <http://192.168.0.254>, the domain server is at 192.168.0.1 > > <http://192.168.0.1> > > > <http://192.168.0.1> and the VoIP server is at 192.168.0.253 > > <http://192.168.0.253> > > > <http://192.168.0.253>. A special user has a static IP with a > system > > > called mobius running Ubuntu and Samba, it is also listed in > > IPcop and > > > can be pinged by name, it is not a domain server just a simple file > > > share. I looks like Windoze can only resolve LAN names if the > system > > > is running Samba. Do I need to setup the domain server to > > resolve LAN > > > names over Samba protocol? > > > > > > C:\Documents and Settings\user>*ping server* > > > Pinging server [192.168.0.1 <http://192.168.0.1> > > <http://192.168.0.1>] with 32 bytes of data: > > > > > > Reply from 192.168.0.1 <http://192.168.0.1> > > <http://192.168.0.1>: bytes=32 time<1ms TTL=64 > > > Reply from 192.168.0.1 <http://192.168.0.1> > > <http://192.168.0.1>: bytes=32 time<1ms TTL=64 > > > > > > Ping statistics for 192.168.0.1 <http://192.168.0.1> > > <http://192.168.0.1>: > > > Packets: Sent = 2, Received = 2, Lost = 0 (0% loss), > > > Approximate round trip times in milli-seconds: > > > Minimum = 0ms, Maximum = 0ms, Average = 0ms > > > C:\Documents and Settings\user>*ping asterisk* > > > Ping request *could not find host asterisk*. Please check the > > name and > > > try again. > > > > > > C:\Documents and Settings\user>*nslookup asterisk* > > > Server: ipcop.localdomain > > > Address: 192.168.0.254 <http://192.168.0.254> > > <http://192.168.0.254> > > > > > > Name: asterisk > > > Address: *192.168.0.253 <http://192.168.0.253> > > <http://192.168.0.253>* > > > > > > ------------------------------------------------------------------------ > > > > > > _______________________________________________ > > > clug-talk mailing list > > > [email protected] <mailto:[email protected]> > > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > > **Please remove these lines when replying > > > > > > _______________________________________________ > > clug-talk mailing list > > [email protected] <mailto:[email protected]> > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > **Please remove these lines when replying > > > > > > > > > > -- > > http://www.Radados.org > > ------------------------------------------------------------------------ > > > > _______________________________________________ > > clug-talk mailing list > > [email protected] > > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > > **Please remove these lines when replying > > > _______________________________________________ > clug-talk mailing list > [email protected] > http://clug.ca/mailman/listinfo/clug-talk_clug.ca > Mailing List Guidelines (http://clug.ca/ml_guidelines.php) > **Please remove these lines when replying > -- http://www.Radados.org
_______________________________________________ clug-talk mailing list [email protected] http://clug.ca/mailman/listinfo/clug-talk_clug.ca Mailing List Guidelines (http://clug.ca/ml_guidelines.php) **Please remove these lines when replying
