Click to See Complete Forum and Search --> : Samba proxy?
gig2k1s
01-17-2003, 02:42 PM
I guess I should explain first. Our new office at work only has a few ports for the network, so we created a simple router using slackware. The routing and everything works, we can mount network drives and all, but we can't let our windows machines join the windows domain. I'm not sure exactly what to do since I have little to no experience, but I'm sure it involves samba. My boss said something like we have to configure samba as a proxy. I have no idea, and haven't been able to find documentation. Can anyone help?
gig2k1s
01-20-2003, 11:16 AM
bump
jumpedintothefire
01-20-2003, 02:02 PM
Can you summit abit more detail about your layout and what you want to do....
gig2k1s
01-20-2003, 04:30 PM
I'll try to explain a bit, but we are all confused about this. In our office, we have a slackware router connected to the campus network. The router is connected to a 16 port switch, and internet functions fine for the workstations. We can map network drives on the workstations, but we can't join the NT domain. It has become a little difficult to be a domain admin when your computer can't even get on the domain. We know that we need to use samba on the router, but neither one of us has played with samba before, and we're not even sure what we need it to do. We just want to be able to have our workstations join the NT domain. Any help?
jumpedintothefire
01-20-2003, 06:19 PM
In our office, we have a slackware router connected to the campus network. The router is connected to a 16 port switch, and internet functions fine for the workstations.
>> so are you masq'd the machines behind the slack box??
>> Your using different network ipaddresses on each side, correct??
but we can't join the NT domain
>> on the other side of the slack box??
>> The problem is that all the connections on the office lan appear to be coming from just the slack box as far as the campus network is concerned.... The pdc will try to connect back to the workstation, see the problem..... One machine should be no problem using port forwarding.....
There was a net bios forwarder floating around but I can't find it at the moment....... I had D/L'ed it but that was serveral months ago(2 years??) I'll see I burned it to cd before my drive bit the dust....
jumpedintothefire
01-20-2003, 06:31 PM
Found it.... Not sure if it will work with a 2.4 kernel
http://nbfw.sourceforge.net/installation.html
gig2k1s
01-21-2003, 11:04 AM
Thanks, that looks like it will work. I'm sending it to my friend now to work on it.
jumpedintothefire
01-21-2003, 11:23 AM
Post the results, I'd like to know if it works and what you did to get it to go. I have no time to play around ATM....
pcghost
01-21-2003, 02:46 PM
Squid and Privoxy are proxies, Samba is a domain controller or workgroup translator. Check out the GUI in my sig. It makes it all easy to figure out..
gig2k1s
01-21-2003, 02:59 PM
We're all a little too stuborn to use a web interface to do anything :). Just stupid slackware people. I'm not sure exactly what they have been doing at work, been busy with classes, but the gist that I got was that my boss wouldn't try to software since the project was dropped in 2001, and that the latest problem is that we can't do domain lookups for some reason. The smaller private LAN works, but the win2k workstations behind the firewall still can't join the windows campus domain. I'll let you know what the logs say if I can get into the office.