|
Home > Archive > Unix administration > March 2005 > Sco 5.0.5 TCP/IP
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| returnoftheyeti@aol.com 2005-03-01, 6:04 pm |
| Hello, I got tossed into working on a SCO Server that is in a
production enviroment. Currently this company uses dummy terminals
accross serveral locations. This all works well and good. I have been
tasked w/ making it talk to a windows 2003 Server. When I first fot to
the SCO box it did not even have a NIC.
I am somewhat familiar w/ Linux and very good with Windows networking,
so I figured I could figure this out with out too much of a problem.
I have inserted the Network card and the SCO OS does see it. I am not
sure how to check the status of the driver, or which modual it is.
ifconfig net1 up does appear to bring up the interface, and next I
configured the IP address using the netconfig command (I gave it
192.168.1.2). All seemed well there and it recompiled the kernel to my
horror. I rebooted and everything came up. NO error messages during
the reboot, and it shows SCO TCP/IP started. Ifconfig net1 shows the IP
address, I can ping 127.0.0.1 and 192.168.1.1. However, I can not ping
any other 192 address. 192.168.1.1 is the router and it accepts pings
just fine from any other machine, and no other machine can ping
192.168.1.2. Trying gives the error "host is down" (I think thats the
error, I am writing this from memory). I have also tried typing "route
add gateway 192.168.1.1" and I get the same error.
I have no idea what to do next. If someone can give me some guidance,
or even point me to some online help, I'd greatly appriciate it.
TIA
Jeremy
| |
| Pat Welch 2005-03-02, 7:51 am |
|
returnoftheyeti@aol.com wrote:
> Hello, I got tossed into working on a SCO Server that is in a
> production enviroment. Currently this company uses dummy terminals
> accross serveral locations. This all works well and good. I have been
> tasked w/ making it talk to a windows 2003 Server. When I first fot to
> the SCO box it did not even have a NIC.
>
> I am somewhat familiar w/ Linux and very good with Windows networking,
> so I figured I could figure this out with out too much of a problem.
>
> I have inserted the Network card and the SCO OS does see it. I am not
> sure how to check the status of the driver, or which modual it is.
> ifconfig net1 up does appear to bring up the interface, and next I
> configured the IP address using the netconfig command (I gave it
> 192.168.1.2). All seemed well there and it recompiled the kernel to my
> horror. I rebooted and everything came up. NO error messages during
> the reboot, and it shows SCO TCP/IP started. Ifconfig net1 shows the IP
> address, I can ping 127.0.0.1 and 192.168.1.1. However, I can not ping
> any other 192 address. 192.168.1.1 is the router and it accepts pings
> just fine from any other machine, and no other machine can ping
> 192.168.1.2. Trying gives the error "host is down" (I think thats the
> error, I am writing this from memory). I have also tried typing "route
> add gateway 192.168.1.1" and I get the same error.
>
> I have no idea what to do next. If someone can give me some guidance,
> or even point me to some online help, I'd greatly appriciate it.
>
> TIA
> Jeremy
>
Try pointing to the router as the default gateway:
As root -
/etc/route add default 192.168.1.1
If the above helps, put the above line in /etc/rc2.d/S85tcp just below
the existing line that starts off /etc/route add xxxxxxxxx. This will
initiate the gateway every time the system is booted.
Then put your primary and secondary DNS resources in the text file
/etc/resolv.conf, like this format:
hostresorder local bind nis
nameserver xx.xx.xx.76
nameserver xx.xx.xx.77
Put any local DNS nameserver 1st obviously.
If you still have a problem, try using traceroute (man traceroute for
info). Your router may be set to deny pings to a certain address range,
and the Unix server falls in that range.
Good luck.
--
----------------------------------------------------
Pat Welch, UBB Computer Services, a WCS Affiliate
SCO Authorized Partner
Unix/Linux/Windows/Hardware Sales/Support
(209) 745-1401 Cell: (209) 251-9120
E-mail: patubb@inreach.com
----------------------------------------------------
| |
| returnoftheyeti@aol.com 2005-03-02, 7:51 am |
| Pat, I appricate your answer. In a Windows enviroment, I dont need a
gateway or any DNS to ping andother IP on the same subnet. I do not
know if this is true for SCO Unix. The router is set to accept all
pings from anywhere, and I can't ping the SCO box from another machine.
I made a typing mistake on my above post, I gave the SCO box
192.168.1.2, and I can ping 192.168.1.2, but I can't ping any other
192.168 number.
Still lost,
Jeremy
| |
| Pat Welch 2005-03-10, 8:49 pm |
| returnoftheyeti@aol.com wrote:
> Pat, I appricate your answer. In a Windows enviroment, I dont need a
> gateway or any DNS to ping andother IP on the same subnet. I do not
> know if this is true for SCO Unix. The router is set to accept all
> pings from anywhere, and I can't ping the SCO box from another machine.
>
>
> I made a typing mistake on my above post, I gave the SCO box
> 192.168.1.2, and I can ping 192.168.1.2, but I can't ping any other
> 192.168 number.
>
> Still lost,
> Jeremy
>
Whats the netmask on the SCO box? It's most likely 255.255.255.0, which
is the default.
With that netmask, you could not ping anything other than 192.168.1.x
addresses. Your post seemed to imply you were failing to ping addresses
outside of that metric. An IP like 192.168.2.x would not be pingable for
example.
As root, enter: netconfig
to look at the current settings.
Perhaps you should look into having a consultant with SCO experience
assist you.
--
----------------------------------------------------
Pat Welch, UBB Computer Services, a WCS Affiliate
SCO Authorized Partner
Unix/Linux/Windows/Hardware Sales/Support
(209) 745-1401 Cell: (209) 251-9120
E-mail: patubb@inreach.com
----------------------------------------------------
|
|
|
|
|