locked
1311 There are currently no logon servers available to logon your request RRS feed

  • Question

  • Sziasztok!

    A targyban jelzett uzenetet kapjak tegnap ota a usereim, akik ket trustolt domain kozotti halozati mappat probalnak megnyitni.
    Eddig ment. Amit eddig probaltam:

     - Trust megszuntetes, ujraepites. - tudtam validalni is, minden gond nelkul.
     - DNS secondaryk torlese, ujra letrhozasa, transfer from master, mukodik.
     - Megosztas megszuntetes, ujra megosztas, jogok kiosztasa. Nah itt van a bibi. Az "A" domain jogosultsagai rendben vannak, viszont ha pl. a "B" domainbol akarok hozzaadni usert v. group-pt akkor jo sok kerdojel jelenlik meg, pedig ha jogosulsagoknak advanced--> find now -val tallozok, szepen hoz minden user es groupot a masik domainbol.

    Valami otlet?

    Mert mar kicsit tanacsatalan lettem.

    jah, szerverek: win2k3 R2 domainenkent 2db.
    DNS - AD integralt.

    Üdv!

    Tamás


    Varga Tamás
    Wednesday, February 11, 2009 8:47 AM

Answers

  • Meg nem teljesen jo, de csak erdekessegkeppen a DC-ben van tartalek, nem hasznalt halokartya. Ezeket most disabled-re tettem, es lass csodat netdiag hibatlan lett :)

    ipconfig -ot meg beletettem login scriptbe, holnap reggel userek ha lepnek be, majd takarit. Aztan kiderul mi lesz.

    Varga Tamás
    • Marked as answer by Othorvath Saturday, March 28, 2009 7:28 PM
    Wednesday, February 11, 2009 1:57 PM

All replies

  • Csak nehany tippem van. Ha a jogosultsagokhoz hozzaadod a B domain csoportjait/felhasznaloit (az Advanced segitsegevel), akkor el tudjak erni? Gondolom a problemas mappa az A domain-ben van, s az A tagjai elerik, nem?

    Az A-bol a B DNS-et, DC-it siman elered? GC is?

    A.

    Wednesday, February 11, 2009 11:10 AM
  • Szia,


    jah "A" domainben van a shared mappa, "A" userei siman elerik. "B" domainbol ha usert addolok hozza, akkor se eri el es csak user sid-jet latom a jogosulsagok advenced fulen, egyszeruen nem tudja kiolvasni a user/group adatokat az "A" domain a "B"-bol. "A" bol elerem a "B" DC-ket, GC-tis, DNS replikal, ezt teszteltem is. "B" domainbol az "A" shared dir-t "A" -s felhasznaloval siman map-elem. Egyszeruen tanacsatalan vagyok.

    Üdv!


    Varga Tamás
    Wednesday, February 11, 2009 12:06 PM
  • Arra tudok csak gondolni, hogy a B domain DC-i, GC nincs a helyzet magaslatan... B-beli eroforrast elersz A es B-beli felhasznaloval? B-n tudsz futtatni egy netdiag, dcdiag-ot?

    A.

    Wednesday, February 11, 2009 12:23 PM
  • netdiag "A" domainben tokeletes:

    DNS test . . . . . . . . . . . . . : Passed
        PASS - All the DNS entries for DC are registered on DNS server '172.16.111.12' and other DCs also have some of the names registered.
        PASS - All the DNS entries for DC are registered on DNS server '172.16.111.14' and other DCs also have some of the names registered.
        PASS - All the DNS entries for DC are registered on DNS server '172.16.111.1' and other DCs also have some of the names registered.
        PASS - All the DNS entries for DC are registered on DNS server '172.16.112.2' and other DCs also have some of the names registered.
        PASS - All the DNS entries for DC are registered on DNS server '172.16.112.3' and other DCs also have some of the names registered.

    netdiag "B" domainben:

    DNS test . . . . . . . . . . . . . : Passed
        PASS - All the DNS entries for DC are registered on DNS server '172.16.112.2' and other DCs also have some of the names registered.
        PASS - All the DNS entries for DC are registered on DNS server '172.16.112.3' and other DCs also have some of the names registered.
        [WARNING] The DNS entries for this DC are not registered correctly on DNS server '172.16.112.1'. Please wait for 30 minutes for DNS server replication.
        [WARNING] The DNS entries for this DC are not registered correctly on DNS server '172.16.111.12'. Please wait for 30 minutes for DNS server replication.
        [WARNING] The DNS entries for this DC are not registered correctly on DNS server '172.16.111.14'. Please wait for 30 minutes for DNS server replication.

    Viszont erdekessegkeppen toroltem minden secondary DNS-t, secondary reverse DNS-t, ujra letrehoztam, ujra sync, es a "B" domain egyik DC-jen sikerult megnyitni a mappat, es nehany kliens is el tudja erni... erdekes......

    Varga Tamás
    Wednesday, February 11, 2009 1:40 PM
  • DNS gond volt? A tobbi kliensen esetleg ipconfig /flushdns? Vagy netalan ujrainditas nem segit?

    A.
    Wednesday, February 11, 2009 1:47 PM
  • Meg nem teljesen jo, de csak erdekessegkeppen a DC-ben van tartalek, nem hasznalt halokartya. Ezeket most disabled-re tettem, es lass csodat netdiag hibatlan lett :)

    ipconfig -ot meg beletettem login scriptbe, holnap reggel userek ha lepnek be, majd takarit. Aztan kiderul mi lesz.

    Varga Tamás
    • Marked as answer by Othorvath Saturday, March 28, 2009 7:28 PM
    Wednesday, February 11, 2009 1:57 PM
  • Ha ujraindul a gep, akkor nem kell az ipconfig /flushdns. Ez a DNS-cache-t uriti, ami ujrainditassal eleve kiurul... Tehat kiveheted a login scriptbol :)

    A.
    Wednesday, February 11, 2009 2:17 PM