-   Linux - Networking (
-   -   Help, what services are needed for a windows to access Linux servers (

Wolfy 07-11-2004 04:09 PM

Help, what services are needed for a windows to access Linux servers
I have been trying to set up Fedora Core 2 on my server and create a LAN that my windows machines can access. But I've changed to many things and did not keep good enough notes on everything I changed (Shame on me!:tisk: )
So I've decided to re install and start from scratch, and I am going to keep better notes on what I'm changing AND make backup copies.

I would like to know all (or as many as I can get) of the services or daemons or programs I will be needing to let these Windows boxes talk to the Linux Server.

I've spent the last month or so working with Linux ( Debian and FC2 ) I am starting to get quite comfortable using it, but I am finding it hard to get up-to-date information on how to setup a network with it.
Peer to peer in windows is easy compared to Linux.

Could somebody please help me? I'm getting frazzled!:(

born4linux 07-11-2004 05:22 PM

for linux to be seen in a windows net neighborhood, install and setup Samba on it. search LQ or, you'll get dozens of hits.

things to watch out:

- samba workgroup name (should be the same asyour windows' pcs)
- firewall setup - samba needs to have these open:

UDP 137 and 138
TCP 139 and 445

heh, u need to make sure that they can ping each other first. :)

Wolfy 07-11-2004 05:45 PM

Okay I got it Install and configure Samba.
But question:
The NIC to the Internet needs firewall right?
And the NIC to network needs to be open.
About pinging I should ping after I setup Samba right? or else they won't see each other right?

sh3ll 07-11-2004 08:46 PM

if i right understand u,, then yes u apply the firewall rules on the outside NIC where u get internet traffic..
about pinging , u should be able to successfuly ping anytime, b4 and after installing samba
caz its something more basic than the samba service, in more technical words , samba works
on the application layer and the ping on the transport layer,, so all the protocols (ip in this situation) should constantly be able to serve all of the layers and applications above it.. got it?
it should ping and it should response all the time!! as pinging is living :)

Wolfy 07-12-2004 01:31 AM

Okay here we go,
I managed to get the simple network to work, permissions and all. But eth0 which connects to the Inernet will not connect (cannot activate). Windows can see the assigned directory in the linux machine but linux can't see the shared directories in the windows machine.

There is no assigned default gateway though (from setup)
Before it was the other way around, (I could access the internet but not the local area network)

Something doen't seem right here?:confused:

Can Somebody explain what is going on and how I can solve this?

sh3ll 07-12-2004 07:35 AM

from what u said ,umean u ve asmall LAN with some windows boxes and one redhat server, and those which we are concerned with rightnow, not the firewall or the internet..

windows can access the shared linux directories? gr8 ,then samba is working probably inthere.
but vice versa isnt working.. u use XP?
if so one thing could prevent linux from accessing the box probably iguess,, just disable
the (simple file sharing) option in winxp...
tell us how it goes.

Wolfy 07-12-2004 09:36 PM

Ohh Right, one thing at a time.:)

Correct one Server Fedora Core 2 (redhat) kernel version2.6.5-1.358smp
Two windows boxes one WinXP Pro and one Win2000 Pro.
There in no Simple Sharing on Windows that i can find, only the [File and Print sharing for microsoft networks]
Do you mean on the linux box?

All times are GMT -5. The time now is 11:22 PM.