Connecting To Windows 2003 Domain Under Rh8?

[tansqrx 0]

I am about to reach through the screen and stangle that scrawny little penguin!Here is my problem. I am at work and need a way to access files and printers on the Windows 2003 domain. I have to use Red Hat Linux 8.0, it is a requirement for the software that I am testing. I have read somewhere that I need at least version 3.0 of Samba but the only version for RH8 is 2.2.5. I have had a similar problem with Evolution. Is there any way of getting connected to my domain or should I just give up?

[Klass 0]

just a suggestion but look on the samba site for help with windows server 2003

https://www.google.com/search?q=samba%2Bser:en-US:official

[saneax 0]

Hi tansqrx,If you want to just access the Windows 2003 Server and access some shares on that server.. you have a few options..1) you have to join your machine to the Win 2003 Server... (which is really complicated)2) you install the latest Samba (in case you need help in that post me back here and then... try this lets say on win2003 you want to access the D share.. assuming the win2003 IP is 192.168.0.10 #>smbclient -L 192.168.0.10 -U Administrator%password {This will list you the shares you can mount } now change to root #>smbmount //192.168.0.10/DSHARE /path/to/mnt -username=Administrator -password=passwordThe #2 depends on the win 2003 Policies, in case the Win2003 is just a standalone server it will work, but if it is configured as a AD, it might not work, in that case #1 is the only option...Take a look at http://forums.xisto.com/no_longer_exists/, they have a cool UI solution to your problem...regards

[xboxrulz1405241485 0]

RH8 is too old to work with any new operating system versions. Samba < 2.2.8 doesn't work with Windows NT based systems. Please upgrade to Fedora Core 4 or other new Linux versions.xboxrulz

[qwijibow 0]

So you have version 2.2.x and you need version 3.x.The 2 obviouse solutions are to update samba, or use a non anchant version of GNU.for example fedora core 4. Or better yet, an up to date version of Redhat Enterprise.

[yordan 10]

tansqrx seems to be at work. This could be probably a work-side problem. Probably at work he has to use Red Hat Linux 8.0 because it's certified for a given purpose (for instance certified for use with an ERP home-made thing), and then he cannot change his redhat version or his Linux version because this means validating again the whole thing against all the possible client/server combinations. So, if he wants to use samba, he has to use samba in this precise Red Hat configuration. And that's why he asks for help.

[tansqrx 0]

tansqrx seems to be at work. This could be probably a work-side problem. Probably at work he has to use Red Hat Linux 8.0 because it's certified for a given purpose (for instance certified for use with an ERP home-made thing), and then he cannot change his redhat version or his Linux version because this means validating again the whole thing against all the possible client/server combinations. So, if he wants to use samba, he has to use samba in this precise Red Hat configuration. And that's why he asks for help.

<{POST_SNAPBACK}>

Thank you yordan this is exectly what I am saying. The requirement for evaluating a piece of software is RH8. The software can not work with any other OS (prob can but this is the world of software engineering and RH8 is baselined). From the many helpful posts I can tell that I am just SOL. I have already setup a RH8 install in VMWare so I suspose all is not lost. Just that VMWare is very slow.

[yordan 10]

Be careful with vmware. Most of operating system communication things do not work on vmware systems.So, your first try should be to install RH8 on a standalone Intel system, with standard connectivity (standard Ethernet board attached to a cable) and test the samba connectivity on it. If it works correctly, then try to add the vmware layer, and verify it's still working. If it works on a standalon machine and does not work on a vmware sub-machine, this means that vmware has to be configured more precisely. For instance, your vmwawe machine is probably a DHCP client from your main host, which is not known from your win2003 as being a master domain controller.Hope this helpedYordan

[saneax 0]

Yep, Vmware has a built in samba started with default, which enables you to share the host files into the gues operating system, hence samba wouldnt work at all... The workaround is to disable the VMWares samba, How ? run... the vmware-config.pl... and when it asks you should it do the host sharing of files, you say no!....cheers