Topic: Windows 2000

[Carthorse]

I know there are some messages already but they don't seem to help me.
I have a Win2000 box at work that I want to use with e-smith to develop a network
E-smith is up and working, the modem is fine, and it found my NIC card.
I have upgraded samba to 2.2.1 and this worked ok (I think)
However, as far as my Win2k box is concerned, there is nothing at the other end of the network.
If I try to join the domain (I have selected DCHP) it denies that such a domain exists. i can't ping out to the address of the e-smith server or from the e-smith server.
I am sure I am doing something really dumb, but being dumb, I don't know what it is!!!
Any help would be gratefully received.

[sclark]

Sounds like your on the right track. Check the subnets on both machines, must be the same. Also, check the workgroup name. By default, the e-smith workgroup is 'e-smith', and windows defaults to 'workgroup'. Change one so they are in the same workgroup, then you should be ok.

[Graham]

IMHO its better to set IP addresses for each machine if you have less than ten
and kee a nice list of them. See if they can ping each other. See if they can see
each other on the network ?

[Carthorse]

I should add that I have Win98 box that works fine, and a Linux box that works fine. I have even dual booted the Win2000 machine in linux and found the server. But I cannot get my Win2000 to find the server!!
I may have to scrub Win2000 and go back to Win98

[Rick Buford]

One thing your post indicates is that you are trying to join a domain using your e-smith box. This would be incorrect. The error that you are seeing is the correct error for trying to join a domain that does not exist. You are actually joining a workgroup, which is essentially a group of like-named machines. Think of a domain as a workgroup with centralized account management (oversimplification, but should get the point across). Verify that both your Win machine and the e-smith server are in the same workgroup, and failing connection then probably indicates hardware failure/misconfiguration somewhere betwixt the two.