VPN na haɗawa, amma SQL Server ya ƙi tabbacin Windows
Shigar VPN na aiki, SQL Server ya ƙi tabbacin Windows: kwatanta asusun ramin da alamar abokin ciniki, sannan karanta auth_scheme a kan uwar garke.
Ramin suna tashi, uwayen garke suna amsa ping, kuma shigar da bayanan har yanzu yana kasawa da kuskuren tabbaci. Wannan haɗin ya zama ruwan dare a kan hanyoyin VPN kuma da wuya yana nufin hanyar sadarwa ta lalace, domin mai sauraro da ake iya isa da shigar da aka karɓa sakamako ne guda biyu daban. Asalin da ya gamsar da ƙofar ba lallai ba ne asalin da abokin cinikin bayanai ke bayarwa. Gano wane asusu ya iso shine dukan aikin.
Alamar: uwar garke mai isa, shigar da aka ƙi
Ƙarewar lokaci yana gaya maka fakitin bai taɓa isa wani mai sauraro ba. Kuskuren tabbaci yana gaya maka mai sauraron ya amsa kuma ya ƙi takardar shaidar. Waɗannan saƙonni biyu suna tura ka zuwa ƙungiyoyi daban, kuma haɗa su yana ɓata kwana ɗaya a kan ka'idojin wuta waɗanda ba su taɓa zama matsala ba.
Lokacin da kuskuren shine gazawar shiga, daina kallon tashoshin. Tambayar da ta rage ita ce wace asalin Windows abokin cinikin ya gabatar, ko uwar garken ya karɓi wannan asalin, kuma ko an warware ta zuwa mai amfani da bayanai mai izini.
Asali biyu, rami ɗaya
Asusun VPN yana tabbatarwa a ƙofar kuma a yawancin turawa yana ƙare a nan. Abokin cinikin bayanai yana gabatar da alamar Windows daban, wadda aka ɗauka daga tsarin da ke tafiyar da shi, ko shigar SQL idan igiyar haɗi ta nemi ɗaya. Mai amfani VPN na gida a ƙofar ba shi da wata alaƙa da yankin da ke ɗaukar SQL Server, kuma ramin ba ya ƙirƙirar irin wannan.
Haɗa na'ura ta sirri da VPN shima baya shigar da ita cikin yankin. Canza sunan asusun gida da daidaita kalmar sirrinsa da mai amfani na yankin ba tsarin yin rajista bane, kuma yana samar da alama wadda mai kula da yankin ba zai karɓa a matsayin wannan mai amfani ba.
Wasu abokan cinikin isa daga nesa na Windows na asali na iya sake amfani da takardar shaidar VPN don albarkatun cibiyar sadarwa lokacin da aka tsara bayanansu haka. Wannan ɗabi'ar ta wani abokin ciniki da bayani ne, ba ta hanyoyin VPN gaba ɗaya ba, don haka tabbatar da ita ga abokin cinikin da ake amfani da shi maimakon ɗauka.
Karanta yanayin da abokin ciniki ya nema
Igiyar haɗi ce ke yanke hukuncin wace hanyar tabbaci abokin ciniki zai bi. Tsaron haɗaɗɗe yana amfani da alamar Windows; nau'in mai amfani da kalmar sirri yana zaɓar shigar SQL. Waɗannan yanayi ne daban a cikin tsarin uwar garke, kuma ɗaya kawai daga cikinsu zai iya kasancewa a kunne don wata ƙoƙarin haɗi.
Server=tcp:sql.lab.example,1433;Database=ops;Integrated Security=SSPI;Encrypt=True;TrustServerCertificate=False;
Komawa zuwa shigar SQL saboda shigar Windows ya kasa hanya ce ta wucin gadi da ke ɓoye tambayar asali, kuma tana buƙatar ƙirƙirar sabon shiga da kalmar sirri duk da haka. Idan turawar na buƙatar tabbacin Windows, riƙe yanayin kuma gyara hanyar asali. Shigar SQL shima yana buƙatar izininsa, don haka hanyar wucin gadi tana sayan asusu na biyu don kulawa.
Hakanan tabbatar da wace manhaja ke haɗawa. Sabis da ke gudana a matsayin asusun tsarin, aiki da aka tsara da taga tambaya mai mu'amala na iya gabatar da alamu uku daban a na'ura ɗaya, kuma na ƙarshe ne kawai ya dace da abin da mai amfani ke gani lokacin da yake gudanar da whoami.
Tambayi uwar garke abin da ta gani da gaske
Uwar garken na iya gaya maka wace shiga ta warware da yadda haɗin ya tabbata. Gudanar da tambayar cikin zaman da ake bincike, domin nasarar haɗin mai gudanarwa daban ba ta tabbatar da komai game da abokin cinikin da ke kasawa.
SELECT ORIGINAL_LOGIN() AS original_login,
SUSER_SNAME() AS current_context;
SELECT auth_scheme, net_transport
FROM sys.dm_exec_connections
WHERE session_id = @@SPID;
Layi na farko yana bambanta shigar da ta buɗe zaman da yanayin tsaro da ke aiki yanzu, kuma suna bambanta a ƙarƙashin kwaikwayo. Na biyu yana ambaton tsarin tabbaci, don haka KERBEROS, NTLM da SQL sun zama gaskiya bayyane maimakon zato. Haɗin da ke ba da rahoton NTLM a inda ka yi tsammanin Kerberos matsala ce ta warware suna ko SPN, ba matsalar kalmar sirri ba.
Lambar kuskure tana ƙara taƙaita shi. Yanayi 5 yawanci yana nufin ba a warware sunan shiga kwata-kwata ba, yanayi 8 yawanci yana nufin kalmar sirri ba ta dace ba, kuma yanayi 11 yana nufin an karɓi takardar shaidar amma isa ga uwar garke ya kasa. Tambayi mai gudanarwa yanayin maimakon dukan saƙon, domin saƙon shi kaɗai yana da shakku da gangan.
| What you observe | What it suggests |
|---|---|
| Timeout, no listener | Route, firewall or wrong port |
| Login failed, state 5 | Name not resolved in the domain |
| Login failed, state 11 | Authenticated but no server access |
| Connected as NTLM | Target name or SPN mismatch |
Lokacin da asalin ya iso kuma Kerberos har yanzu ya kasa
Idan uwar garken tana ganin asalin Windows da ake so kuma tabbacin haɗaɗɗe har yanzu yana kasawa, musayar da kanta ce matsalar. Kerberos yana buƙatar babban sunan sabis (SPN) da aka yi wa asusun sabis na SQL rajista da abokin ciniki da ke neman sabis da sunan da ya dace da shi. Haɗawa da adireshin IP ba zai iya dacewa da SPN na tushen suna ba, kuma laƙabi zai iya dacewa ne kawai idan shima an yi masa rajista. Duba sunan da abokin ciniki ya buga kafin komai, domin haɗin da ke aiki da sunan mai masauki kuma ya kasa da IP yana kwatanta wannan matsalar daidai.
Ka roƙi mai gudanarwa ya duba asalin da aka yi rajista da asusun sabis maimakon ƙirƙirar SPN biyu ta hanyar gwaji da kuskure. Rajista biyu suna haifar da gazawa lokaci-lokaci waɗanda suka fi wahalar gano su fiye da ainihin matsalar.
Bayan tabbaci ya yi aiki, shigar har yanzu tana buƙatar mai amfani da bayanai da izini. Nasarar shigar VPN, nasarar shigar Windows da izinin karanta wani tebur wasu sakamako ne guda uku daban, kuma kowanne ya cancanci nasa binciken kafin a rufe tikitin.