How to setup client(window) server(linux) connection and install samba
 

hello there. i'm trying to setup simple client server connection. i choose xubuntu as linux server and window 7 as client. i must achive this three option.
1-remote access to server from client
2-client can upload file to server
3-client can download file from server.
help me guys, or maybe give me some good website to refer. thanks alot.

a fast google search for HOWTO configure SAMBA Ubuntu will provide that information for you.

so far as connecting the win7 box it is no different then mapping a network drive. depending on how your LAN is configured you might have to use the IP of the server from win7, unless you have a proper local DNS server running that win7 may or may not properly read the FQDN of your Linux server as MS does things backwords in the DNS world.

Hi there,

not necessarily. Samba can also act as a WINS server, mimicking the way Windows's "Network Neighborhood" would deal with host names when Windows boxes share files/directories among each other. Agreed, Windows versions after XP have some evil magic in them, but IMO that should still work.

[X] Doc CPU

keep in mind that WINS was for all MS OSs pre-win2k. since win2k WINS is no longer the default for MS name service... MS moved to DNS, a broken vs, but DNS none the less. WINS can still be enabled in win7, but it has to be manually configured and activated.

http://windows.microsoft.com/en-US/w...CP-IP-settings

Hi there,

are you really telling me that WINS is obsolete since 2k/XP? Am I getting that right?
Well, that would explain a lot. However, telling from the symptoms, Windows 2000 still seems to use WINS, while XP doesn't. I assume that because I've never had any trouble hooking a few Win2k workstations together and share files among them, while the same task is a PITA with two or more XP boxes. But you're right, as soon as there's a DNS on the local network, it works like a charm.

Do you have more information on that readily available? The pre-Win7 thing, of course. I can search for it, of course, but you sound like you've got some insight.

Alright, but I don't touch Win7 and later except with protective gloves. ;-)

Hm. That doesn't tell me more than what I would've guessed anyway. The interesting part (the Advanced tab) is missing ...

[X] Doc CPU

starting with win2k (both server and workstation as they run the exact same kernel) MS "claimed" to move from their closed standards for networking (WINS) to "open source" DNS, Kerberos, LDAP, etc... for building their AD network to replace the out dated model of PDC and BDC of NT4 and older (that would be win98 and older as well).

WINS is active in win2k, but is not the "best practice" for connection. The reason it was activated by default is due to win98 and winNT3/4 still require WINS for connection without Novel.

winXP was the first MS OS that dropped the default setting of WINS being active as win2k3 server, the same kernel as XP, started depreciation of WINS.

what im talking about with the broken DNS, DHCP, Kerberos, LDAP is the naming under MS is backwards from the IEEE standard for all of those services. This is it "broken" but works.

if you are fully in a MS network you will not notice, but as soon as you add a real OS to the LAN you will notice that things dont function as expected.

under win7 the advance tab for networking is ONLY available for win7 Pro and Ultimate. any lower vs. of win7 and you will not have the advance tab.

hope that answers the questions.

Hi there,

well, it's a bit weird to speak of WINS as a closed standard; after all, it has been well-known at least since Windows 98, though not officially disclosed. It's been the same with FAT32 for years: Everyone knew how it worked, many companies and independent developers implemented their own FAT32 drivers, even though MS hadn't yet disclosed it. Reverse engineering can be great fun. ;-)

Agreed. But yet it's simple, it's robust - and it simply works, because every compliant client can become a server just like that.

Oh, Novell. Another PITA.

Yes, I will. I did. In a network with only XP machines, I couldn't get file and printer sharing to work among them. No way. Add one Windows 2000 box, and everything's fine, because it will immediately be elected as a primary WINS server. Alternatively, add a DNS server. But a bunch of XP Home or XP Pro among their own kind won't get you anywhere. That's my conclusion anyway.

Veto! The two XP machines I set up for a customer last year worked fine within my network, where they were the only Windows clients among some Linux machines with a few Sambas and one DNS server being present. But the same two XP machines on their own at the customer's site couldn't access each other. Fortunately, that wasn't a requirement of my customer, but it would've simplified my work.

But thanks a lot for your consideration.

[X] Doc CPU