Hi Bob,

Thanks, and I'll surely check all this out.

The DOMAIN *is* set on one of the other machines - it is a regular modem access backup for work access.
The WINS is set to 'use DHCP...' on two of the machines - those with the DOMAIN set. Other has it disabled.
IP Address on all is set to "Obtain IP address automatically.
Bindings is set for Client for MS Network and File and Printer Sharing for MS Network.

I just replaced the cable and connector and it made no difference! Device Manager reports adapter as "operating correctly'.

Will keep at it. Thanks for the help to date!

Jim N

>>>3. Make sure TCP/IP is bound to the adapter!
>>>
>>I presume I can say that it *is* when I see an arrow from TCPIP to SMC Ether..
>
>OK... I think so... but, you can click on the adapter, press properties, and go to bindings.
>
>
>>I wouldn't know how to "setup the TCPIP" much less specify an address. I do know that I have not needed to specify any kind of 'address' to have the network working before. I assumed that NIC card had this on it.
>>
>Um... nope... only ArcNet works that way. If you go to your network setup, highlite the TCP/IP that is pointing to your physical adapter, press properties... There is a IP Address tab there. Each machine must have it's own in 'Specify IP Address' section... There is also a 'Bindings' here, make sure it shows as binded to client for Ms Networks. DNS and Wins should be set as Disabled.
>
>
>>I was instructed to set up a DOMAIN which is available only through dial-up after I have booted. But without that I cannot communicate with the office! I have no idea how all this works!
>>
>This may be the problem... that access control has alot to do with how the computer identifies itself on the network. Change to shared level access. I assume you only have the domain set up on the machine that doesn't work on your local network?
>
>>Thanks again, and I'll let all know when it is solved.
>
>Sure!
>
>BOb