Re: Networking Fedora in a Windows Environment

Timothy Brooks wrote ..
Does anyone have a reference on Networking Fedora Core on a Windows
Network. The Windows Network is a small peer-to-peer office network
with about 6 computers and a couple of networked devices (printers).
There is no server and we use file sharing. Thank you.


The first package you should look into is called SAMBA.

Log into KDE (K Desktop Environement if you installed it). From the 'start menu' select System Settings -> Server Settings -> Samba. Select 'Add Share' and select your home directory '/home/youraccountname'.

-or-

I think by default, SAMBA does not run. You can start it by opening a terminal and typing the command 'service smb start'. Although you'll probably need super user access so from the terminal type 'su' and enter the root password when prompted. Once SAMBA is running you can probably access the configuration through a web interface called SWAT. Open your web browser (probably firefox) and enter the URL 127.0.0.1:901. If it says no connection available, then you'll have to enable it as a service. Unfortunately, I got some other things ot do and don't have time to explain that one now.

-or-

Something else you might be interested in seeing is a program called WEBMIN (www.webmin.com). This is a web based interface to managing your computer. It has access to managing programs users hardware, everything. It also has an interface to configure SAMBA. You can download a .rpm (Redhat Package Management) file which is easy to install. Again, I can't explain that now, out of time...

Good Luck
--
fedora-list mailing list
fedora-list@xxxxxxxxxx
To unsubscribe: https://www.redhat.com/mailman/listinfo/fedora-list

Relevant Pages

  • Re: The Hard Problem for Behaviorists
    ... correct low level abstractions to define the operation of the brain with - ... Do you not know how computers work? ... you can think of this type of network like you ... when you drop a marble in hole X1, ...
    (sci.cognitive)
  • Re: Networks : Workgroups and Domains. How Do I Use Them?
    ... I think the problem is from my lack of understanding whether these machines are together as a workgroup or domain. ... If I want to configure solely for a workgroup network, then I would think I do not need to provide a domain name, and vice versa for a domain network. ... It's not clear whether any of your computers is running Windows 2000 *Server.* If not, you don't have a "domain" and shouldn't be using domain names. ... Problems sharing files between computers on a network are generally caused by 1) a misconfigured firewall or overlooked firewall; or 2) inadvertently running two firewalls such as the built-in Windows Firewall and a third-party firewall; and/or 3) not having identical user accounts and passwords on all Workgroup machines; 4) trying to create shares where the operating system does not permit it. ...
    (microsoft.public.windowsxp.network_web)
  • Re: {workgroup}"...is not accessible" after removing NWLINK
    ... I generally reboot the machine whenever I make network ... >problem is a browse service that won?t run on the XP machine using the TCP/IP ... >?The browser has forced an election on network ... >> computer, and one, or preferably two, of the Windows 98 computers. ...
    (microsoft.public.windowsxp.network_web)
  • Re: Help with 070-217
    ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)
  • RE: Help with 070-217
    ... The network contains 25,000 computers. ... > single Windows 2000 domain named research.contoso.com. ... > Server computers that are configured as domain controllers. ...
    (microsoft.public.cert.exam.mcse)