FreeTDS Development Group

["James K. Lowden" <jklowden AT schemamania.org>]

Hello everyone, 

I can't access my Sybase server over the network.  It's not like I didn't
change anything; I did.  It's just that it's definitely not a FreeTDS
question.  

What I did:

I upgraded my TurboLinux server to Red Hat 7.3.  To get Sybase going
again, I recreated the /opt/sybase-11.9.2 tree with tar, and remounted the
device partition at 
/opt/sybase-11.9.2/Devices.  I wrote a little script to set up the locale
stuff the way it had been in TurboLinux.  I fired up startserver,
connected with their isql, and voila, I was in server heaven.  

>From outside the box, though, it's another story, and not a happy one. 
Maybe Tolstoy was onto something there.  

I can connect to the server's telnetd.  I made all the usual entries in
/etc/services and I deleted /etc/hosts.allow.  (The RH manual says lack of
hosts.allow means all hosts are allowed.  That's confirmed by telnetd
working.)  I fussed with /etc/hosts, because some time ago Michael Peppler
mentioned that Linux hosts often have faulty domain notions, that Sybase
doesn't like: 

$ cat /etc/hosts
# Do not remove the following line, or various programs
# that require network functionality will fail.
127.0.0.1               sandbox.schemamania.org sandbox
localhost.localdomain localhost
192.168.1.12 sandbox.schemamania.org

But still no joy.  Any suggestions?  Is running through a complete Sybase
reinstall necessary or even recommended?  I should think one could backup
and restore an installation, but then I should have thunk what I did
woulda worked.  Or is there a magic switch I overlooked?  As you can
probably tell, I'm not a Linuxhead.  I run it to run Sybase.  

Many thanks, 

--jkl