PC Review
Forums
Newsgroups
Windows Vista
Windows Vista Security
Unable to UNC to a share on a Windows 2003 domain
Forums
Newsgroups
Windows Vista
Windows Vista Security
Unable to UNC to a share on a Windows 2003 domain
![]() |
Unable to UNC to a share on a Windows 2003 domain |
|
|
Thread Tools | Rate Thread |
|
|
#1 |
|
Guest
Posts: n/a
|
recently installed build 5365 and have enjoyed it... this is whats happening
thus far The machine is not a member of anything other than a workgroup. I try to UNC to a domain share (Example: \\SERVER\SHARE) and I am continually being prompted for authentication, I tried providing NETBIOSNAME\LOGINID and password, that doesnt work. I tried FQDN@DOMAIN.COM and password and that doesnt work... 1. I have turned off the firewall 2. Turned off UAC I dont know what else it could be? Anyone? |
|
|
|
#2 |
|
Guest
Posts: n/a
|
"I try to UNC to a domain share (Example: \\SERVER\SHARE) and I am
continually being prompted for authentication" You sure it shouldn't be \\DOMAIN\Username There would have to be an account in the Domain with access to the share I suspect to do this, you would then use \\DOMAIN\Username to authenticate get access to share. -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta "James L VanDusen" <james@vandusenfamily.org> wrote in message news:2789F46E-D19F-4160-8006-C801FE3E923F@microsoft.com... > recently installed build 5365 and have enjoyed it... this is whats > happening thus far > > The machine is not a member of anything other than a workgroup. I try to > UNC to a domain share (Example: \\SERVER\SHARE) and I am continually being > prompted for authentication, I tried providing NETBIOSNAME\LOGINID and > password, that doesnt work. I tried FQDN@DOMAIN.COM and password and that > doesnt work... > 1. I have turned off the firewall > 2. Turned off UAC > > I dont know what else it could be? Anyone? |
|
|
|
#3 |
|
Guest
Posts: n/a
|
Correct... however it keeps prompting (says incorrect username/password) Im
telling ya its some form of protection (the firewall is off but I do notice that if I open anything new it needs to add it to the firewall?!?). Wierd. Anyone else with this issue? James "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message news:%23Ukct0haGHA.4772@TK2MSFTNGP05.phx.gbl... > "I try to UNC to a domain share (Example: \\SERVER\SHARE) and I am > continually being prompted for authentication" > You sure it shouldn't be \\DOMAIN\Username > > There would have to be an account in the Domain with access to the share I > suspect to do this, you would then use \\DOMAIN\Username to authenticate > get access to share. > -- > -- > Andre > Windows Connected | http://www.windowsconnected.com > Extended64 | http://www.extended64.com > Blog | http://www.extended64.com/blogs/andre > http://spaces.msn.com/members/adacosta > > "James L VanDusen" <james@vandusenfamily.org> wrote in message > news:2789F46E-D19F-4160-8006-C801FE3E923F@microsoft.com... >> recently installed build 5365 and have enjoyed it... this is whats >> happening thus far >> >> The machine is not a member of anything other than a workgroup. I try to >> UNC to a domain share (Example: \\SERVER\SHARE) and I am continually >> being prompted for authentication, I tried providing NETBIOSNAME\LOGINID >> and password, that doesnt work. I tried FQDN@DOMAIN.COM and password and >> that doesnt work... >> 1. I have turned off the firewall >> 2. Turned off UAC >> >> I dont know what else it could be? Anyone? > > |
|
|
|
#4 |
|
Guest
Posts: n/a
|
its some how Vista is blocking maybe udp/tcp 137-139 possibly which is
passing the credentials... The strange part was it was working, and I have tested this on various domains now. James "James L VanDusen" <james@vandusenfamily.org> wrote in message news:%237ybF6haGHA.3612@TK2MSFTNGP03.phx.gbl... > Correct... however it keeps prompting (says incorrect username/password) > Im telling ya its some form of protection (the firewall is off but I do > notice that if I open anything new it needs to add it to the firewall?!?). > > Wierd. > > Anyone else with this issue? > > James > > "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message > news:%23Ukct0haGHA.4772@TK2MSFTNGP05.phx.gbl... >> "I try to UNC to a domain share (Example: \\SERVER\SHARE) and I am >> continually being prompted for authentication" >> You sure it shouldn't be \\DOMAIN\Username >> >> There would have to be an account in the Domain with access to the share >> I suspect to do this, you would then use \\DOMAIN\Username to >> authenticate get access to share. >> -- >> -- >> Andre >> Windows Connected | http://www.windowsconnected.com >> Extended64 | http://www.extended64.com >> Blog | http://www.extended64.com/blogs/andre >> http://spaces.msn.com/members/adacosta >> >> "James L VanDusen" <james@vandusenfamily.org> wrote in message >> news:2789F46E-D19F-4160-8006-C801FE3E923F@microsoft.com... >>> recently installed build 5365 and have enjoyed it... this is whats >>> happening thus far >>> >>> The machine is not a member of anything other than a workgroup. I try >>> to UNC to a domain share (Example: \\SERVER\SHARE) and I am continually >>> being prompted for authentication, I tried providing NETBIOSNAME\LOGINID >>> and password, that doesnt work. I tried FQDN@DOMAIN.COM and password >>> and that doesnt work... >>> 1. I have turned off the firewall >>> 2. Turned off UAC >>> >>> I dont know what else it could be? Anyone? >> >> > |
|
|
|
#5 |
|
Guest
Posts: n/a
|
I am not at work today, so I am unable to try this, may Zack will be able to
provide a useful response thank I did. Have you tried adding the ports to the Windows Firewall you specified? "udp/tcp 137-139 " -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta "James L VanDusen" <james@vandusenfamily.org> wrote in message news:O$p3x$haGHA.3524@TK2MSFTNGP04.phx.gbl... > its some how Vista is blocking maybe udp/tcp 137-139 possibly which is > passing the credentials... > > The strange part was it was working, and I have tested this on various > domains now. > > James > "James L VanDusen" <james@vandusenfamily.org> wrote in message > news:%237ybF6haGHA.3612@TK2MSFTNGP03.phx.gbl... >> Correct... however it keeps prompting (says incorrect username/password) >> Im telling ya its some form of protection (the firewall is off but I do >> notice that if I open anything new it needs to add it to the >> firewall?!?). >> >> Wierd. >> >> Anyone else with this issue? >> >> James >> >> "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message >> news:%23Ukct0haGHA.4772@TK2MSFTNGP05.phx.gbl... >>> "I try to UNC to a domain share (Example: \\SERVER\SHARE) and I am >>> continually being prompted for authentication" >>> You sure it shouldn't be \\DOMAIN\Username >>> >>> There would have to be an account in the Domain with access to the share >>> I suspect to do this, you would then use \\DOMAIN\Username to >>> authenticate get access to share. >>> -- >>> -- >>> Andre >>> Windows Connected | http://www.windowsconnected.com >>> Extended64 | http://www.extended64.com >>> Blog | http://www.extended64.com/blogs/andre >>> http://spaces.msn.com/members/adacosta >>> >>> "James L VanDusen" <james@vandusenfamily.org> wrote in message >>> news:2789F46E-D19F-4160-8006-C801FE3E923F@microsoft.com... >>>> recently installed build 5365 and have enjoyed it... this is whats >>>> happening thus far >>>> >>>> The machine is not a member of anything other than a workgroup. I try >>>> to UNC to a domain share (Example: \\SERVER\SHARE) and I am continually >>>> being prompted for authentication, I tried providing >>>> NETBIOSNAME\LOGINID and password, that doesnt work. I tried >>>> FQDN@DOMAIN.COM and password and that doesnt work... >>>> 1. I have turned off the firewall >>>> 2. Turned off UAC >>>> >>>> I dont know what else it could be? Anyone? >>> >>> >> > |
|
|
|
#6 |
|
Guest
Posts: n/a
|
It seems to work fine here... instead of trying to connect to the server
name itself, go for the IP address and see if this helps. Does seem to be a bug perhaps though. Make sure your servers have been notched up to accept Windows 2000 and above though - can't remember off the top of my head, but it's in Active Directory Users & Computers somewhere. -- Zack Whittaker » ZackNET Enterprises: www.zacknet.co.uk » MSBlog on ResDev: www.msblog.org » Vista Knowledge Base: www.vistabase.co.uk » This mailing is provided "as is" with no warranties, and confers no rights. All opinions expressed are those of myself unless stated so, and not of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared that up! --: Original message follows :-- "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message news:%23nQc0ViaGHA.3812@TK2MSFTNGP04.phx.gbl... >I am not at work today, so I am unable to try this, may Zack will be able >to provide a useful response thank I did. > > Have you tried adding the ports to the Windows Firewall you specified? > "udp/tcp 137-139 " > -- > -- > Andre > Windows Connected | http://www.windowsconnected.com > Extended64 | http://www.extended64.com > Blog | http://www.extended64.com/blogs/andre > http://spaces.msn.com/members/adacosta > > "James L VanDusen" <james@vandusenfamily.org> wrote in message > news:O$p3x$haGHA.3524@TK2MSFTNGP04.phx.gbl... >> its some how Vista is blocking maybe udp/tcp 137-139 possibly which is >> passing the credentials... >> >> The strange part was it was working, and I have tested this on various >> domains now. >> >> James >> "James L VanDusen" <james@vandusenfamily.org> wrote in message >> news:%237ybF6haGHA.3612@TK2MSFTNGP03.phx.gbl... >>> Correct... however it keeps prompting (says incorrect username/password) >>> Im telling ya its some form of protection (the firewall is off but I do >>> notice that if I open anything new it needs to add it to the >>> firewall?!?). >>> >>> Wierd. >>> >>> Anyone else with this issue? >>> >>> James >>> >>> "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message >>> news:%23Ukct0haGHA.4772@TK2MSFTNGP05.phx.gbl... >>>> "I try to UNC to a domain share (Example: \\SERVER\SHARE) and I am >>>> continually being prompted for authentication" >>>> You sure it shouldn't be \\DOMAIN\Username >>>> >>>> There would have to be an account in the Domain with access to the >>>> share I suspect to do this, you would then use \\DOMAIN\Username to >>>> authenticate get access to share. >>>> -- >>>> -- >>>> Andre >>>> Windows Connected | http://www.windowsconnected.com >>>> Extended64 | http://www.extended64.com >>>> Blog | http://www.extended64.com/blogs/andre >>>> http://spaces.msn.com/members/adacosta >>>> >>>> "James L VanDusen" <james@vandusenfamily.org> wrote in message >>>> news:2789F46E-D19F-4160-8006-C801FE3E923F@microsoft.com... >>>>> recently installed build 5365 and have enjoyed it... this is whats >>>>> happening thus far >>>>> >>>>> The machine is not a member of anything other than a workgroup. I try >>>>> to UNC to a domain share (Example: \\SERVER\SHARE) and I am >>>>> continually being prompted for authentication, I tried providing >>>>> NETBIOSNAME\LOGINID and password, that doesnt work. I tried >>>>> FQDN@DOMAIN.COM and password and that doesnt work... >>>>> 1. I have turned off the firewall >>>>> 2. Turned off UAC >>>>> >>>>> I dont know what else it could be? Anyone? >>>> >>>> >>> >> > > |
|
|
|
#7 |
|
Guest
Posts: n/a
|
Zack,
yeah its not a DNS issue, it connects fine either way, just wont successfully authenticate... Im very stressed about this as it appears everything else is working... on the test machines you have are they stand alone (not part of a domain) because that is what I am testing. These are not member workstations to any domain just workgroup. James "Zack Whittaker" <admin@zacknet.co.uk> wrote in message news:%23jWgppiaGHA.1228@TK2MSFTNGP02.phx.gbl... > It seems to work fine here... instead of trying to connect to the server > name itself, go for the IP address and see if this helps. Does seem to be > a bug perhaps though. Make sure your servers have been notched up to > accept Windows 2000 and above though - can't remember off the top of my > head, but it's in Active Directory Users & Computers somewhere. > > -- > Zack Whittaker > » ZackNET Enterprises: www.zacknet.co.uk > » MSBlog on ResDev: www.msblog.org > » Vista Knowledge Base: www.vistabase.co.uk > » This mailing is provided "as is" with no warranties, and confers no > rights. All opinions expressed are those of myself unless stated so, and > not > of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared > that up! > > --: Original message follows :-- > "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message > news:%23nQc0ViaGHA.3812@TK2MSFTNGP04.phx.gbl... >>I am not at work today, so I am unable to try this, may Zack will be able >>to provide a useful response thank I did. >> >> Have you tried adding the ports to the Windows Firewall you specified? >> "udp/tcp 137-139 " >> -- >> -- >> Andre >> Windows Connected | http://www.windowsconnected.com >> Extended64 | http://www.extended64.com >> Blog | http://www.extended64.com/blogs/andre >> http://spaces.msn.com/members/adacosta >> >> "James L VanDusen" <james@vandusenfamily.org> wrote in message >> news:O$p3x$haGHA.3524@TK2MSFTNGP04.phx.gbl... >>> its some how Vista is blocking maybe udp/tcp 137-139 possibly which is >>> passing the credentials... >>> >>> The strange part was it was working, and I have tested this on various >>> domains now. >>> >>> James >>> "James L VanDusen" <james@vandusenfamily.org> wrote in message >>> news:%237ybF6haGHA.3612@TK2MSFTNGP03.phx.gbl... >>>> Correct... however it keeps prompting (says incorrect >>>> username/password) Im telling ya its some form of protection (the >>>> firewall is off but I do notice that if I open anything new it needs to >>>> add it to the firewall?!?). >>>> >>>> Wierd. >>>> >>>> Anyone else with this issue? >>>> >>>> James >>>> >>>> "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message >>>> news:%23Ukct0haGHA.4772@TK2MSFTNGP05.phx.gbl... >>>>> "I try to UNC to a domain share (Example: \\SERVER\SHARE) and I am >>>>> continually being prompted for authentication" >>>>> You sure it shouldn't be \\DOMAIN\Username >>>>> >>>>> There would have to be an account in the Domain with access to the >>>>> share I suspect to do this, you would then use \\DOMAIN\Username to >>>>> authenticate get access to share. >>>>> -- >>>>> -- >>>>> Andre >>>>> Windows Connected | http://www.windowsconnected.com >>>>> Extended64 | http://www.extended64.com >>>>> Blog | http://www.extended64.com/blogs/andre >>>>> http://spaces.msn.com/members/adacosta >>>>> >>>>> "James L VanDusen" <james@vandusenfamily.org> wrote in message >>>>> news:2789F46E-D19F-4160-8006-C801FE3E923F@microsoft.com... >>>>>> recently installed build 5365 and have enjoyed it... this is whats >>>>>> happening thus far >>>>>> >>>>>> The machine is not a member of anything other than a workgroup. I >>>>>> try to UNC to a domain share (Example: \\SERVER\SHARE) and I am >>>>>> continually being prompted for authentication, I tried providing >>>>>> NETBIOSNAME\LOGINID and password, that doesnt work. I tried >>>>>> FQDN@DOMAIN.COM and password and that doesnt work... >>>>>> 1. I have turned off the firewall >>>>>> 2. Turned off UAC >>>>>> >>>>>> I dont know what else it could be? Anyone? >>>>> >>>>> >>>> >>> >> >> > > |
|
|
|
#8 |
|
Guest
Posts: n/a
|
Windows 2000 and above though - can't remember off the top of my head, but
it's in Active Directory Users & Computers somewhere. I thought you could only do this if you are setting up the domain for the first time or a new forest? -- -- Andre Windows Connected | http://www.windowsconnected.com Extended64 | http://www.extended64.com Blog | http://www.extended64.com/blogs/andre http://spaces.msn.com/members/adacosta "Zack Whittaker" <admin@zacknet.co.uk> wrote in message news:%23jWgppiaGHA.1228@TK2MSFTNGP02.phx.gbl... > It seems to work fine here... instead of trying to connect to the server > name itself, go for the IP address and see if this helps. Does seem to be > a bug perhaps though. Make sure your servers have been notched up to > accept Windows 2000 and above though - can't remember off the top of my > head, but it's in Active Directory Users & Computers somewhere. > > -- > Zack Whittaker > » ZackNET Enterprises: www.zacknet.co.uk > » MSBlog on ResDev: www.msblog.org > » Vista Knowledge Base: www.vistabase.co.uk > » This mailing is provided "as is" with no warranties, and confers no > rights. All opinions expressed are those of myself unless stated so, and > not > of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared > that up! > > --: Original message follows :-- > "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message > news:%23nQc0ViaGHA.3812@TK2MSFTNGP04.phx.gbl... >>I am not at work today, so I am unable to try this, may Zack will be able >>to provide a useful response thank I did. >> >> Have you tried adding the ports to the Windows Firewall you specified? >> "udp/tcp 137-139 " >> -- >> -- >> Andre >> Windows Connected | http://www.windowsconnected.com >> Extended64 | http://www.extended64.com >> Blog | http://www.extended64.com/blogs/andre >> http://spaces.msn.com/members/adacosta >> >> "James L VanDusen" <james@vandusenfamily.org> wrote in message >> news:O$p3x$haGHA.3524@TK2MSFTNGP04.phx.gbl... >>> its some how Vista is blocking maybe udp/tcp 137-139 possibly which is >>> passing the credentials... >>> >>> The strange part was it was working, and I have tested this on various >>> domains now. >>> >>> James >>> "James L VanDusen" <james@vandusenfamily.org> wrote in message >>> news:%237ybF6haGHA.3612@TK2MSFTNGP03.phx.gbl... >>>> Correct... however it keeps prompting (says incorrect >>>> username/password) Im telling ya its some form of protection (the >>>> firewall is off but I do notice that if I open anything new it needs to >>>> add it to the firewall?!?). >>>> >>>> Wierd. >>>> >>>> Anyone else with this issue? >>>> >>>> James >>>> >>>> "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message >>>> news:%23Ukct0haGHA.4772@TK2MSFTNGP05.phx.gbl... >>>>> "I try to UNC to a domain share (Example: \\SERVER\SHARE) and I am >>>>> continually being prompted for authentication" >>>>> You sure it shouldn't be \\DOMAIN\Username >>>>> >>>>> There would have to be an account in the Domain with access to the >>>>> share I suspect to do this, you would then use \\DOMAIN\Username to >>>>> authenticate get access to share. >>>>> -- >>>>> -- >>>>> Andre >>>>> Windows Connected | http://www.windowsconnected.com >>>>> Extended64 | http://www.extended64.com >>>>> Blog | http://www.extended64.com/blogs/andre >>>>> http://spaces.msn.com/members/adacosta >>>>> >>>>> "James L VanDusen" <james@vandusenfamily.org> wrote in message >>>>> news:2789F46E-D19F-4160-8006-C801FE3E923F@microsoft.com... >>>>>> recently installed build 5365 and have enjoyed it... this is whats >>>>>> happening thus far >>>>>> >>>>>> The machine is not a member of anything other than a workgroup. I >>>>>> try to UNC to a domain share (Example: \\SERVER\SHARE) and I am >>>>>> continually being prompted for authentication, I tried providing >>>>>> NETBIOSNAME\LOGINID and password, that doesnt work. I tried >>>>>> FQDN@DOMAIN.COM and password and that doesnt work... >>>>>> 1. I have turned off the firewall >>>>>> 2. Turned off UAC >>>>>> >>>>>> I dont know what else it could be? Anyone? >>>>> >>>>> >>>> >>> >> >> > > |
|
|
|
#9 |
|
Guest
Posts: n/a
|
No this is normal ability since NT days... its basically causes NT to prompt
for authentication when accessing a share on a domain... james "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message news:udcfBTjaGHA.1192@TK2MSFTNGP04.phx.gbl... > Windows 2000 and above though - can't remember off the top of my head, but > it's in Active Directory Users & Computers somewhere. > > I thought you could only do this if you are setting up the domain for the > first time or a new forest? > -- > -- > Andre > Windows Connected | http://www.windowsconnected.com > Extended64 | http://www.extended64.com > Blog | http://www.extended64.com/blogs/andre > http://spaces.msn.com/members/adacosta > > "Zack Whittaker" <admin@zacknet.co.uk> wrote in message > news:%23jWgppiaGHA.1228@TK2MSFTNGP02.phx.gbl... >> It seems to work fine here... instead of trying to connect to the server >> name itself, go for the IP address and see if this helps. Does seem to be >> a bug perhaps though. Make sure your servers have been notched up to >> accept Windows 2000 and above though - can't remember off the top of my >> head, but it's in Active Directory Users & Computers somewhere. >> >> -- >> Zack Whittaker >> » ZackNET Enterprises: www.zacknet.co.uk >> » MSBlog on ResDev: www.msblog.org >> » Vista Knowledge Base: www.vistabase.co.uk >> » This mailing is provided "as is" with no warranties, and confers no >> rights. All opinions expressed are those of myself unless stated so, and >> not >> of my employer, best friend, Ghandi, my mother or my cat. Glad we cleared >> that up! >> >> --: Original message follows :-- >> "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message >> news:%23nQc0ViaGHA.3812@TK2MSFTNGP04.phx.gbl... >>>I am not at work today, so I am unable to try this, may Zack will be able >>>to provide a useful response thank I did. >>> >>> Have you tried adding the ports to the Windows Firewall you specified? >>> "udp/tcp 137-139 " >>> -- >>> -- >>> Andre >>> Windows Connected | http://www.windowsconnected.com >>> Extended64 | http://www.extended64.com >>> Blog | http://www.extended64.com/blogs/andre >>> http://spaces.msn.com/members/adacosta >>> >>> "James L VanDusen" <james@vandusenfamily.org> wrote in message >>> news:O$p3x$haGHA.3524@TK2MSFTNGP04.phx.gbl... >>>> its some how Vista is blocking maybe udp/tcp 137-139 possibly which is >>>> passing the credentials... >>>> >>>> The strange part was it was working, and I have tested this on various >>>> domains now. >>>> >>>> James >>>> "James L VanDusen" <james@vandusenfamily.org> wrote in message >>>> news:%237ybF6haGHA.3612@TK2MSFTNGP03.phx.gbl... >>>>> Correct... however it keeps prompting (says incorrect >>>>> username/password) Im telling ya its some form of protection (the >>>>> firewall is off but I do notice that if I open anything new it needs >>>>> to add it to the firewall?!?). >>>>> >>>>> Wierd. >>>>> >>>>> Anyone else with this issue? >>>>> >>>>> James >>>>> >>>>> "Andre Da Costa [Extended64]" <andred25@hotmail.com> wrote in message >>>>> news:%23Ukct0haGHA.4772@TK2MSFTNGP05.phx.gbl... >>>>>> "I try to UNC to a domain share (Example: \\SERVER\SHARE) and I am >>>>>> continually being prompted for authentication" >>>>>> You sure it shouldn't be \\DOMAIN\Username >>>>>> >>>>>> There would have to be an account in the Domain with access to the >>>>>> share I suspect to do this, you would then use \\DOMAIN\Username to >>>>>> authenticate get access to share. >>>>>> -- >>>>>> -- >>>>>> Andre >>>>>> Windows Connected | http://www.windowsconnected.com >>>>>> Extended64 | http://www.extended64.com >>>>>> Blog | http://www.extended64.com/blogs/andre >>>>>> http://spaces.msn.com/members/adacosta >>>>>> >>>>>> "James L VanDusen" <james@vandusenfamily.org> wrote in message >>>>>> news:2789F46E-D19F-4160-8006-C801FE3E923F@microsoft.com... >>>>>>> recently installed build 5365 and have enjoyed it... this is whats >>>>>>> happening thus far >>>>>>> >>>>>>> The machine is not a member of anything other than a workgroup. I >>>>>>> try to UNC to a domain share (Example: \\SERVER\SHARE) and I am >>>>>>> continually being prompted for authentication, I tried providing >>>>>>> NETBIOSNAME\LOGINID and password, that doesnt work. I tried >>>>>>> FQDN@DOMAIN.COM and password and that doesnt work... >>>>>>> 1. I have turned off the firewall >>>>>>> 2. Turned off UAC >>>>>>> >>>>>>> I dont know what else it could be? Anyone? >>>>>> >>>>>> >>>>> >>>> >>> >>> >> >> > > |
|
|
|
#10 |
|
Guest
Posts: n/a
|
"James L VanDusen" <james@vandusenfamily.org> wrote:
> The machine is not a member of anything other than a workgroup. I try to > UNC to a domain share (Example: \\SERVER\SHARE) and I am continually being > prompted for authentication, I tried providing NETBIOSNAME\LOGINID and > password, that doesnt work. I tried FQDN@DOMAIN.COM and password and that > doesnt work... I saw someone else reporting that kind of behavior/problem as new to 5365, specifically accessing domain-based server from workgroup-only Vista 5365 machine. I'm actually seeing that issue myself, within the workgroup, from Vista to existing XP SP2 machines. If the credentials I've used for logging into Vista 5365 don't transparently authenticate me to the remote XP machine, sometimes the credentials are accepted in the authentication prompt that comes up, but other times no amount of correctly-entered credentials will succeed. If you set the Vista username and password to match the necessary account information for accessing the remote machine, it works every time without issue (therefore not seeming to be any sort of "firewall" or "can't get there from here with those credentials" issue). This pure-workgroup scenario was new to 5365; i.e. I've been accessing these same XP SP2 machines successfully (after being prompted for authentication because the accounts normally don't match) in 5342 and earlier. Alan Adams |
|
![]() |
|
| Thread Tools | |
| Rate This Thread | |
|
|

Main Page 

