Can't ping SCO Unix 3.2 Host from remote locations

Can't ping SCO Unix 3.2 Host from remote locations

Post by Michael Sweede » Fri, 05 Feb 1999 04:00:00



I have a client with an SCO Unix 3,2 Server running TCP/IP. Ther were 15
PCs installed for this client, some within the office and some on a WAN
via a T1 connection. There is also an NT Server on the LAN. All PCs both
on the LAN and the WAN can access each other and the NT Server, but only
the local PCs can connect to the Unix box. The PCs are all the same make
and configured the same. The remote PCs cannot ping the Unix box
successfully. All the PC support and the hardware support folks say that
the network is fine, and that the problem lies with the Unix box. This
baffles me. Any suggestions would be GREATLY appreciated!
Thanks,
Michael
--
L. Michael Sweeden
108 Foxwood Circle
Oliver Springs, TN 37840
Phone: (423)435-7025
Fax: (423)435-5023


 
 
 

Can't ping SCO Unix 3.2 Host from remote locations

Post by Tony Lawrenc » Sat, 06 Feb 1999 04:00:00



> I have a client with an SCO Unix 3,2 Server running TCP/IP. Ther were 15
> PCs installed for this client, some within the office and some on a WAN
> via a T1 connection. There is also an NT Server on the LAN. All PCs both
> on the LAN and the WAN can access each other and the NT Server, but only
> the local PCs can connect to the Unix box. The PCs are all the same make
> and configured the same. The remote PCs cannot ping the Unix box
> successfully. All the PC support and the hardware support folks say that
> the network is fine, and that the problem lies with the Unix box.

But of course that's all the useless morons had to say, wasn't it?

If they truly had any brains, they'd be able to tell you WHY you have
this problem.  I don't expect incompetent Microsoft weenies to actually
be able to figure out how to CHANGE anything on a unix box, and frankly
I'd prefer that most of them kept their clumsy fingers out of it, but if
they know where the problem is, then by gum they ought to know WHAT the
problem is.

Most likely this is a routing issue.  As the WAN PC's can access the NT,
they *probably* have a route to that network, that's *probably* the same
network your SCO box is on, and what you *probably* need is a route BACK
to the WAN from your SCO box.

Ask the little twits to describe the networks and the routing tables on
the PC side and then we can tell you what you need to do on the SCO box.

--

SCO ACE
SCO articles, help, book reviews: http://www.aplawrence.com

 
 
 

1. Get 'cannot connect to host', yet can ping remote host!!

Thanks for reading this.

When I connect to my internet service provider,
I get a dynamic IP address (viewable in /var/log/messages),
am able to 'ping' the remote IP address, yet when I try to run
'lynx' I get 'cannot connect to host'.

BTW, I did try to run Netscape, but got colormap errors. I decided
to back away from Netscape for now.

Any ideas are appreciated.

Keith

2. Alphanumeric sorting with trailing blanks

3. SCO 3.2 Unix Host dropping telnet sessions

4. [PATCH] New fs to control access to system resources

5. SCO Unix 3.2 & hosts.deny

6. Suppressing named verbosity

7. SCO rel 3.2 v 2.0 - location of /bin/su file

8. SPARCUS Question

9. Can't install uod426d on sco unix v/386 rel 3.2 ver 2.0

10. Can't ping the host name or host IP address from host.

11. can't ping host or host IP from host ?

12. SCO 3.2 v4.2 host devolopment system

13. sco 3.2 v4.2 host development system