SCO

I just installed a new server with sco 5.0.7 and installed SP5. I installed the server on site but windows computers can't access through Powerterm Pro. It indicates that it is connected but no login appears. netstat -an won't run, it just hangs until I press CTRL-BACKSPACE. The old server, which is also 5.0.7 but SP1, does accept the connections and shows the Login. The connection is TCP/IP

Can anyone help me with this?

Try

Code:

trace netstat -an

Because it might hang before showing the hanging syscall, compare it with your working system.

It's been a few years since I used SCO in anger but I do remember that you needed to configure the number of pseudo-ttys that you wanted.

This was done with:

Code:

# mkdev ptty

or possibly the SCO admin shell:

Code:

# scoadmin

If you change the number of ptty's then the management took will ask if you want to relink the kernel and you need to say yes. Also, say yes to rebuilding the kernel environment.

At this stage just try the 'mkdev ptty' command and it will tell you how many ptty's you have configured already.

Since you are getting no response from netstat, you should confirm that tcp is running.
#/etc/tcp stop
#/etc/tcp start
At the console, try 'telnet localhost'. You should get a new login prompt. Type <ctrl>] to get a telnet> prompt and enter quit.
Confirm that the network configuration for ip address and netmask is consistent at both the SCO and Windows ends.
Confirm that the Powerterm configuration points to the new system.
Assuming that you have the graphical interface working, try opening the web browser and opening the web page on your router.
The initial installation sets up 16 pseudo ttys so that is not likely to be the problem.

@jgt.......I had assumed that the network (tcp) was running because ping works.

telnet localhost also hangs. What else to look for?

---------- Post updated at 10:17 AM ---------- Previous update was at 09:56 AM ----------

Also, I can ping the server from another machine but I can't ping out. Not even the machine itself.

Are you listening for a telnet connection? Try:-

Code:

netstat -na | grep LISTEN | grep "\.23"

Do you get any output?

If so, what process owns port 23 (probably inetd):-

Code:

lsof -i tcp:23 | grep LISTEN

What is telnetd record defined as in /etc/inetd.conf or if you are xinetd then you might have to past the content of /etc/xinetd.d/telnet

I apologise for not being very familiar with SCO, just a brief foray quite a few years ago to get a server running for an actuarial quotation engine - and that never worked so we disposed of the SCO server too.



Robin