It's been a while since I did this, but I remember there being very specific instructions to follow in the Samba docs for joining an NT domain. Look through /usr/share/doc/samba. I've never used SWAT, so I don't know if that will do it all for you -- it might not. Gook luck.
Charles Nardino...
If I'm not mistaken, there are entries you can make in /etc/ppp/options and/or /etc/ppp/pap-secrets to set the ip addresses that are assigned. I think I read this in the man pages. You can also have dial-in users determine their own ip addresses in the WinDUN settings. I've gotten this far...
Skanx is right -- mgetty with the AutoPPP option in the login.conf works for me. You also have to add a line to /etc/ppp/pap-secrets:
* * "" *
This makes users' passwords serve as secrets. I can log in with Linux and mount NFS shares with no problem. My Win98/NT clients...
I've gotten a Linux (RH6.2) server to join an NT domain. All the other stations can see and can map shares from the Samba server. However, Samba cannot find anything on the network, not even itself. All the other machines here are set to "Use DHCP for WINS resolution." I can't...
ccprgrmr,<br><br>The Knowledgebase solution worked for me:<br><br>1. delete the Hatten.tty font<br><br>2. start your install from a command line in your CD root directory with the /y switch, e.g. D:\setup.exe /y<br><br>This forces Office 97 to edit the registry, evidently getting rid of Office...
OK -- these MS Knowledge Base articles work:<br><br>Q241141<br>Q235279<br>Q235280 <p>Charles Nardino<br><a href=mailto:cnardino@bellatlantic.net>cnardino@bellatlantic.net</a><br><a href= > </a><br>
Just found several Access97 vs. Access2000 proposed solutions at MS support site -- will try them tomorrow, follow-up here. <p>Charles Nardino<br><a href=mailto:cnardino@bellatlantic.net>cnardino@bellatlantic.net</a><br><a href= > </a><br>
We mistakenly purchased a version of Office 2000 (Small Business, I think) that doesn't include Access. I figured we could just go on using Access97 after the Office2000 installation, but then noticed that all the access database icons had been changed from the 97 version to the 2000...
Thanks to everyone for your suggestions. I'm afraid the outfit in question is too big to accomodate two little "Linux freaks" trying to "break into" their network. We've decided instead to "hog" just two stations for ourselves, with Linux on one of them and Win95...
Thanks again for your help, AndyBo. I had just checked out some of the very things you suggested and am now really confused. Our two Linux machines are getting addresses in the range 10.10.*.*, but nearby Win95 machines are 248.*.*.*. We were told we should use our ISP as our domain...
Thank you for your help, AnydBo. My experience is pretty limited, especially when it comes to mixing with NT servers. Let me add some of the details. We have 4 NT servers serving about 300 Win95 stations. We just set up these 2 Linux stations to experiment with. I originally assigned class...
I've just installed two RH6.1 stations on an NT network. Their IP addresses are DHCP-assigned at boot OK, but then I can't get them to see each other unless I check what address has been assigned to each, after which I can at least get them to ping each other. That's about it. They don't seem...
I just read this thread -- a month late -- because I think I'm going to have the same problem soon. I would love to know what the solution was, but all I can see of the final message (from blh) is:<br>
<br>
Thanks for the help but the solution was quite simple, all I needed to do was add the...
After applying SP3, you fixed the registry to accept plain text passwords, didn't you? Maybe SP5 undoes that and you have to do it again. I've been holding off on SP5 myself for just this sort of reason. Maybe there are other things SP5 does too, but I haven't heard of anything yet. Try...
This site uses cookies to help personalise content, tailor your experience and to keep you logged in if you register.
By continuing to use this site, you are consenting to our use of cookies.