Šta je novo?
Od:
Filteri

Mac & Windows 2003 domen

Twix

Twix

Čuven
VIP član
Učlanjen(a)
18.12.2001
Poruke
2,695
Poena
679
E ovako, nisam bas pretrazivao detaljno tako da se unapred izvinjavam :S:

Naime, kolega je kupio laptop Apple iMac (Core2Duo,1Gb Ram....bla,bla) sa 10.4 Mac OS X Panter-om...

Inace mreza mi je Windows 2003 (DC) sa puno korisnika,i sve radi kako valja :)

E sada, njega sam uspeo da konektujem na mail (pop, ne exchange jer koristim mdaemon), a i kupice u ponedeljak Microsoft Office za Mac, tako da ce to da bude OK...
Uspeo sam da ga i autentifikujem kroz proxy (web marshal) tako da i internet radi, ali:

1. Dali Mac moze da pripada windows 2003 domenu?

2. Ne moze da vidi share-ove sa servera jer mi stalno Mac izbacuje neku cudnu poruku kada otkucam njegov username/pass (probao sam i sa domen\username....)....ako moze malo pomoci :S: (u ponedeljak cu napisati sta kaze jer sada ne mogu da se setim).


Naravno, lep je izazov (i izguracu pre ili kasnije, on me je inace pitao dali da uzme Mac tj. dali cu moci da ga podrzim u mrezi, a ja sam mu rekao "za sada ne, ali izguracu" i "...or at least I’ll die trying" :d ....
Bice to jedno lepo iskustvo :)

Hvala

:wave:

P.S.Sada sam video mali info ispod ove sobe koji kaze "Zaseban forum za one koji ne mešaju jabuke i kruške".....

E pa izvinte :D
 
Poslednja izmena:
1. Moze - Apps / Utilities / Directory access
2. Mac moze da pristupa share-ovima u Windows mrezi i postuje prava pristupa koja su setovane od strane admina (u prevodu ako ja kao x.y korisnik nemam pravo pristupa direktorijumu n, dobicu PRAZAN direktorijum).
 
Evo me bas sada za tom famoznom Mac masinom....
Office je sredjen, i skoro sve (na internetu je ocigledno :)), ali nikako ne mogu da prikazem share-ove na serveru...
Pod autentikacionim protokolima sam ostavio samo active directory, i tada uopste ne vidim mrezu, a kada instaliram SMB/CIFS protokol dodatno (tu inace stavim samo ime workgroup-e, posto mi ne dozvoljava da ukucam wins server), onda vidim sve racunare u mrezi ali kada kliknem na server na kome su shareovi on mi izbaci autentikaciju, a nakon unosenja korisnickog imena/sifre (naravno, tacni su) kaze "The alias Server could not be opened, because the original item cannot be found."
Imam opciju delete alias, fix alias, i ok.....naravno nista od ovoga mi bas ne pomaze :S:

Help please...

:wave:
 
Desktop - Go - Connect to server

I onda kucaj nesto tipa:
smb://mojserver/

i trebalo bi da prodje ok sa sve auth.
 
Poslednja izmena:
Evo opet sa ovog lepog Mac-a :)

Ma ne vredi, kucao sam i ime servera i IP adresu, i username@domain sa sifrom i administrator i administrator@domain (sve probane sifre su 100% tacne).....nikako...

Samo mi kaze da ne moze da me "zakaci" jer korisnicko ime ili sifra nisu tacne (a kao sto rekoh, jesu 200%)...

Jos neke lude ideje koje bih mogao da probam?

Da ne zaboravim da dodam da server (masinu) uredno pingujem iz terminala i preko IP adrese i imena servera sto ce reci da je i DNS tu i radi...



P.S.Zvuci loodo, ali i pored ovih problema koje imam sa ovim Mac-om, i dalje bih ga posedovao umesto mog hp laptop-a :D
 
Poslednja izmena:
:D

i ja sam imao isti problem!!! ne znam zbog cega (***, zaboravio sam) ali bash pod Windows 2003 serverom ne mozes da se ulogujes sa Mac-a! odnosno ne mozes da pristupis ni jednom share-u!

e sad, ta masina koja mi je bila po Win2003 serverom je letela iz kuce i na njenom mestu je WinXP gde ne postoji taj problem.

nazalost ne mogu tacno da se setim kako sam resio to sa Win2003 serverom ali znam da je do setovanja windowsa: u security policy mu je nesto ukljuceno/iskljuceno i zbog toga Mac ne moze da mu pristupi ali nema sanse da se setim sta! :(

EDIT: a evo ga i resenje :)
http://allinthehead.com/retro/218/accessing-a-windows-2003-share-from-os-x

In a nutshell, the cause of the problem is the default security policy on Windows 2003 Server being set to always encrypt network connections under all circumstances. Whilst this is fine for most clients (especially Windows clients, understandably), the version of SMB that Panther uses doesn’t support encrypted connections. Apparently this support exists in Samba 3, but not on the version OS X uses. The solution is to change the security policy to use encryption when it’s available and not otherwise. Here’s how.

From Administrative Tools, open Domain Controller Security Settings.
Go to Local Policies then Security Options.

Scroll down to find the entry Microsoft network server: Digitally sign communications (always). Set this to Disabled.

The only thing left to do is to reload the security policy, as changes don’t otherwise take effect for some time. Open up a command window and type:

gpupdate
Kliknite za proširenje...
 
Poslednja izmena:
Hah :S:

Na to sam naleteo pre jedno 15 minuta posto sam lutao internetom...
Updateovao sam policu na serveru i idalje nista...
Cak sam downloadovao i instalirao Microsoft UAM, ali i sa time za sada slaba vajda :(
 
To je to...

kovacm spasao si me glavobolje :)

Podesio sam polise predhodno, ali pogresno :S:

Sada sam ispravio i radi veoma fino...

Verujem da ce ponosni vlasnik ove masine sada biti zadovoljan...


Hvala vam svima puno !

:wave:
 
Ajde da izvucem sa onog sajta ukoliko izbrisu ili slicno...

Znaci kad neko naleti na slicnu zavrzlamu, evo resenja kojie radi super :


Microsoft Windows Server has a some vaguely-worded options which must be disabled to allow OS X's Samba to connect. I never did fix the "name or password is incorrect" error connecting via Samba to my Windows 2000 Server install, so I always passed data back and forth using an XP machine. Seeking to end that kluge with my new Windows 2003 Server install, I hacked everything I could find on the OS X side to no avail. I finally gave up and turned to the Domain Server for salvation. Eventually, I found the right settings:

Start -> All Programs -> Administrative Tools -> Domain Controller Security Policy. You can ignore any errors about truncated strings ... gotta love one-button alerts. Then navigate into Local Policies: Security Options, and set the following:
Microsoft Network Server: Digitally sign communications (always): DISABLED
Microsoft Network Server: Digitally sign communications (if client agrees): ENABLED
Now, if you want the Server to be able to connect to the Macs on the network, or any Samba server (I think), set the following in the same Local Policies: Security Options area:
Microsoft Network Client: Digitally sign communications (always): DISABLED
Microsoft Network Client: Digitally sign communications (if server agrees): ENABLED
And finally, if you want the domain's Windows boxes to be able to connect to the Mac/Samba, set the following:
Domain Member: Digitally encrypt or sign secure data channel (always): DISABLED
Domain Member: Digitally encrypt secure data channel (when possible): ENABLED
Domain Member: Digitally sign secure data channel (when possible): ENABLED
I suppose these same policies are found in a similar location in Windows 2000 Server, but I'm not going to reinistall it just to know. Why all of this was so hard to find and/or figure out, I don't know -- it seems pretty simple once I collected it all from about 10 different places.

Warning: This hint lowers your network's security a bit, use at your own risk.

:wave:
 
moga si samo i headline ostaviti, cisto da neko preko googla jos lakse nadje tekst na benchu :D
 
Morate se prijaviti ili registrovati da odgovorite ovde.
Nazad
Vrh Dno