Fedora og windows i Nettverk

[Myrsve]

her om dagen hadde jeg lan. på lanet tenkte jeg å prøve å se om jeg kunne få tilgang filene de andre delte i nettverket, men når jeg skrude på maskinen så fikk jeg ikke noen IP. så det jeg lurer på er hvordan får jeg ip når jeg bruker fedro core 2 og de andre bruker Windows XP. alle var koblet til en switch.

[objorkum]

Var det en DHCP server i nettverket da? Eller brukte de faste IPer?

[Myrsve]

Alle pcene var tilkoblet en slik switch. alle windows pcene var stilt inn på å motta ip automatisk

[kyrsjo]

Sagt på en annen måte: Var det internett - som typisk er levert fra en ruter? Hadde windowsboksene "automatisk privat adresse"?

 

Det med fildeling windows/FC2 er det mulig du må:

Hi,

 

You don't have to open high-ports.

 

add 137:udp and 138:udp (for netbios-ns and netbios-dgm) to your firewall. An iptstate I just did shows a 137/udp for both src and dest to my WINS server., and various 138/udp all over the subnet. You do have an WINS server running on the network right?  If you do your /etc/samba/smb.conf file should have the following

 

  wins server = nn.nn.nn.nn

where nn.nn.nn.nn is your WINS server.  If this Samba server is doing the name serving, then you need to have this line

  wins support = yes

(not commented out) and then you must comment out the

  wins server = nn.nn.nn.nn

line (since you can't be a name server client and server at the same time)

Plus you should make sure your

domain master = no

and

preferred master = no

or are both commented out (unless you are going to be the domain master or subnet master "browse-list" master.)

 

Here is mine running as a client (notice the comment ";")

/etc/samba/smb.conf

---<snip>----

# Windows Internet Name Serving Support Section:

# WINS Support - Tells the NMBD component of Samba to enable it's WINS Server

;  wins support = yes

 

# WINS Server - Tells the NMBD components of Samba to be a WINS Client

#      Note: Samba can be either a WINS Server, or a WINS Client, but NOT both

  wins server = 192.168.50.127

---<snip>----

 

Hope this helps.  - Plus FWIW, Network Neighborhood never really did work right even in an all Windows world  -- that's why they went with a directory service in W2K.

 

Andrew

 

> -----Original Message-----

> From: Kyrre Ness Sjobak

> Sent: Wednesday, October 20, 2004 07:19 PM

> To: 'For testers of Fedora Core development releases'

> Subject: Re: Network Servers (where is my workgroup?)

>

> *urk*

>

> I was hoping there was some "easy solution" such as "puch port blah:udp

> and blah:tcp open"

>

> Why does windows need to make things complicated?

>

> ons, 20.10.2004 kl. 21.20 skrev Matthew Miller:

> > On Wed, Oct 20, 2004 at 09:15:15PM +0200, Kyrre Ness Sjobak wrote:

> > > Just out of curiosity: which ports do i have to open to make it work?

> >

> > Off the top of my head, I think you need to allow all UDP packets destined

> > for ports above 1024 that originate from ports 137 or 138. But you may want

> > to get confirmation on that from someone who knows what they're talking

> > about. I'm lucky enough that I have no need to deal with this "talking to

> > Windows" issue in my own life.

 

[objorkum]

Altså om det ikke var noen DHCP server i nettverket får ikke Linux IP. Windows setter automatisk en 169.x.x.x IP når den ikke mottar IP etter en viss tid, derfor KAN Windows burker få kontakt selv om de ikke mottar en IP, noe som ikke er en god løsning i det hele tatt. Windows søker rimelig ofte på nytt etter å motta IP og da mister man tilkoblingen en liten periode. Bruk faste IP-adresser!

Endret 29. oktober 2004 av objorkum

[Myrsve]

Har fåt det til nå takk for hjelpen alle sammen