Discussion Locked

Can't connect to SCObox using servr name

0 helpful
7 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.
For some reason I lost the ability to connect to my SCO openserver 5.05 using the server name. I have to connect using the IP address.We don't use DNS.To fix I had to go to the users NT PC's and add the server to the NT host file.I never had to do this before;what did I lose?

7 replies

by cpfeiffe

It may have been identified in WINS. It may have been part of your NT network neighborhood if you used a product like CIFS to translate Unix/Windows file systems. Lots of things come to mind, but those are the main two. If they aren't it try emailing me at my alias and I'll share some more.

by shanghai sam

In order to connect via telnet, ftp etc..
using a unix host name, some sort of resolution needs to happen. On an NT network this can be done via WINS. It should like that is not the case here.
With that ruled out I would look at DNS. Are you running internal DNS ?

A work around for remote host name resolution is to create a file on the remote windows client C:\windows\hosts
(This is not the lmhosts file)

create an entry link this
# For example:
#
102.54.94.97 rhino.acme.com
38.25.63.10 x.acme.com

This will allow the remote win clients to resolve the host name independantly on anything else.

-Danny

by shanghai sam

Install Vision FS. This will broadcast a hostname thoughout your network. This is actually sco's answer to file and printer sharing between open server and windows. We use it for not only sharing files and editing scripts from our desktop, but italso does remote printing off unix boxes and windows boxes. Not to mention it's free. The licensing is based on your server license so there is nothing to buy.

This discussion is closed to new replies.