Topic: Windows 2000 Domain Controller issues

[Spencer Fornaciari]

Hey,
I'm new to e-smith and I just installed SME5 up with hopes of setting it up
as the domain controller for my network.  The other machines are windows
2000 machines.  I followed the upgrade of samba Dan Brown wrote up.

Here is the problem...the systems clearly are reaching the server as their
ip address, etc are being determined by it.  I tried setting them as members
of the domain but got the error: "the specified domain domain either does
not exist or could not be contacted".  Then I tried and setup the windows
systems to be part of the same workgroup as my sme server.  For a while this
worked and I could even reach it via network neighborhood but now that
functionality stopped.  I can still access the server manager via internet
explorer and still am having my ip determined, etc.  I'm just curious if
anyone has any idea about how to fix this and get them setup as members of
the domain or any idea what might be causing this.  Thanks.

[Gerald Jansen]

I attempted to setup with a domain and with a workgroup. In each instance I am unable to connect to the server or its ibays. Version 5 seems to have critical problems that I have never encountered in earlier versions. I have used e-smith since 3.0 and have never had problems that seem only too obvious in 5.0.

[J Strome]

I'm running SME 5, and connecting to it with two Win2K Pro workstations.  With both systems I've been able to view all the ibays, and read/write isn't a problem either.  In fact, as I type this I'm copying 3 650 MB ISO images across to my home dir on my SME 5 box with no problems.  Permissions seem to work as well, I can only see the iBays that my userid has access to.

I didn't do anything special to the configuration, just made sure that my workstations belonged to the correct workgroup, and that's it.

Are your copies of Win2k up to date w/the latest MS ServicePacks?  I know at one point there were some filesharing issues with win2k, but the packs supposedly took care of that.

[Spencer Fornaciari]

Yup, Service Pack 2...and yes I can view them in Network Neighborhood again...but connecting to the domain doesn't work still.J Strome wrote:

[Alejandro]

same problem to me!
Im not able to "see" the server from the w2k wstation, but i'm able to work from w98se and millenium?
my w2k ws is service pack 2  (and I think it's ok with config but who knows with W2k)
and e-smith box  is mitel sme v5 with all blades aplied and Dan Brown's step by step followed samba upgrade how to

(by the way in the how to first samba package is referenced (download address) as samba-2.2.1a......711rh70i386.rpm and then in the rpm installation instruction, is referenced as 2.2.1a......713.i386.rpm.... sorry if I'm missing something . but does it means something should I consider installing a new version of samba?
Maybe if Dan reads this he could clarify things.

Alejandro

[rob fantini]

Hello,

 I've thethe same problem with a win98 pc which I upgraded to win2000..

 I've 2 other win2000 pc's  which had a fresh install, and do not have the problem.

 the error on the win2000 side is 'unable to browse the network'
 'the network is not present or not started'

 I'm able to connect to the net with win2000 going thru sme 5.0 then to the dsl modem..

 I'm stilll working on this, have updated the win2000 pc a few times ..
 I can ping the win2000 pc from sme.

  I'll work on this further tomorrow.. Any ideas?

Rob

[alejandro]

Rob:
I was trying a few things more and then start thinking about protocols.
If you can ping to win2k pc from server or anyother workstation and you can't see it in windows network, problem could be protocols.
windows 2000 assumes you are upgrading from a win NT PDC and BDC network schema, which has chaged to the new win2k networking schema so probably you are still using netbeiu and "sam" authentication method.
Ale

[rob fantini]

I got it going, thiss is what I did

1- delete the existing network setup.

2- add and accept defaults for

 tcp/ip
 client for microsoft networks
  windows file and printer sharing.

 after that I was able to search and browse the local network. i could then access samba shares.

[rob]

Hello,
  This is a correction to my prior note.

 With what I did i can 'browse' the network. I thought this was the same as 'join the domain'  but may be wrong.  I just use a few win2000 boxes and some linux mandrake workstations..
  Prior to what I did, samba shares could not be 'seen' on the network.  after that they could.
 
 
 

 Using win98 the

[karlos]

i've got the same problem:
w2k-pro -----> boxes
samba ------> pdc
and can't join the boxes to the domain.
boxes can see the samba shares, etc.., but can't be joined to the domain.

[Gregg La Baw]

See http://myezserver.com/docs/mitel/samba-upgrade-howto.html. This works on 5.X and 4.12.