Can't see SCO server

[joeblough]

cannot see SCO from NT server or 98 workstations- even 98 machines who belong to the SCO server domain. CAN ping, have common protocols and advanced file print server running.<br>
<br>
Any ideas?!?!<br>
<br>
blake

 

[AndyBo]

When you say you've got common protocols running, which ones exactly? I think you need to have NetBEUI on the SCO box for the MS boxes to see it.<br>
<br>
Also, is the domain you're referring to the TCP/IP domain, or the Windows Networking domain?

 

[joeblough]

NetBeui is running on both types of machines and it's an SCO domain called scodomain along with a windows network called ntdomain. both within the same private address 172.17.1.x-- 255.255.255.0 subnet.<br>
<br>

 

[AndyBo]

This is where I hold my hands up and admit that I've never used SCO Advanced File Print server <br>
<br>
Here's some random thoughts anyway...<br>
<br>
Do you have any routers between the two Windows boxes and the SCO box? From experience, NetBEUI (whether over TCP/IP or not) doesn't work too well over routed networks... I'm probably way off here, cos all the machines you're using are on the same network...<br>
<br>
Is there any kind of browse tool on the SCO box? If so, can it see itself?<br>
<br>
Also, try changing &quot;scodomain&quot; on the SCO box to be &quot;ntdomain&quot; - see if the SCO box suddenly appears. If it does, I'm not sure what the fix may be, apart from to leave the SCO box in &quot;ntdomain&quot;...<br>
<br>
What kind of authorisation is taking place between the SCO box and the NT servers? I'm pretty sure the SCO box will need to &quot;log in&quot; to the NT network to be viewable/view other boxes... Are you using plaintext passwords? I don't think these work any more with NT unless you start hacking registry entries.<br>
<br>
Finally, using a hammer to crack a nut (;^), maybe you might want to take a look at Samba (<A HREF="

http://www.samba.org"

TARGET="_new">

http://www.samba.org</A>

and pick your nearest mirror). I've had this compiled, up and serving file store and printers to a Windows network within half a day of downloading it. Might be worth a try.<br>
<br>
Hope this has stirred a few thoughts, even if it's not helped

 

[Timmeh]

I'm totally new to SCO Unix and am trying to network with a Windows 2000 machine which can Ping the SCO computer perfectly. However, when I try to ping from the SCO computer only 1 packet will be received and I then get the error message

&quot;Ping interrupted whilst trying ot reslove IP address. Check Domain Name Resolver (SFF) Config?&quot;

Can anybody give me a clue what this means or how to fix it? Thanks.

 

[Nostradamus]

Did you ping it using ip-adress or hostname?
Try ping using ip-address.
modify /etc/hosts with hostname and ip-address. Then try pinging using hostname.
/Sören

 

[Megabitman]

I've used AFPS quite a bit and have been pleased with the results. I have not used it with Win2K (I've done enough NT combinations to count tho) but either protocol should work (obviously TCP/IP is the protocol of choice for both OSes these days). Keep in mind that when you install tcp on SCO, you will provide it a domain name (e.g. scodomain???); that domain may or may not be the same as the Windows domain that you will tell it during the installation of AFPS (e.g. ntdomain). I personally have never set up the DNS stuff under SCO and the implementation under Win2K is not too bad so I would use the Win2K box for your DNS action (additionally, Win2K REALLY wants to be the end-all so you need to setup the DNS in Win2K to keep the bootups from dragging on your Win2K workstations. Is your SCO box a secondary domain server, stand-alone or what? If it is a stand-alone, you'll need to setup the trusts between the domains ( the easiest way on the SCO box is to use the User Manager application loaded onto a 98 machine - see astools folder on the SCO box . If it is a secondary server, it should have been authenticated during the install process... Give me a few more details and I'll see what I know.

 

[Timmeh]

I can ping the SCO computer with using the IP address but not using the hostname. Still when pinging IP addresses from the SCO machine only 1 ping is successful I then get the error message that I mentioned before.

 

[stanhubble]

Timmeh

The problem is definitely your ip->hostname resolution.
ping tries to resolve the hostname when you use the ip address, by doing a reverse arp lookup. These are the entries in your dns zone called
1.17.172.in-addr.arpa (using blake's example).

If you are not using dns then both machines must be defined in you &quot;hosts&quot; files and should be fully qualified and i usually find it useful to include a nickname of just the host portion.

q1.q2.q3.q4 host.domain host

you may also want to check the /etc/resolv.conf file on the sco machine to see where/how it is trying to do the resolution.

hth

stan