Home | Contact Us | FAQ | Search & Site Map | Link to Us
Sign In | Join | Other 45 Sites in Network
Home
Discussion GroupsWindows VistaWindows XPWindows MeWindows 98Windows 95Virtual PCInternet ExplorerOutlook ExpressWindows MediaSecurity
Related Topics
MS Server ProductsMS OfficePC HardwareMore Topics ...

Windows Forum / Windows Vista / Networking / May 2008

Tip: Looking for answers? Try searching our database.

vista pc won't access network shared folders

Thread view: 
Enable EMail Alerts  Start New Thread
Thread rating: 
karonz - 28 May 2008 18:58 GMT
We have a network domain, all XP pro compters, though the domain controller
is NT.  I have successfully joined this vista pc, and can 'see' all of the
computers and servers on the domain, BUT cannot access any of the shared
folders.
Can't map to them which is what we usually do, can't browse to them, it asks
for a username and password but will not authenticate using good credentials,
actually will not even authenticate using the server credentials.
I have exhaustively checked the network settings but do not know where else
to look.
I am using our standard network dns, wins, gateway and IP in TCP/ IPV4
We will soon be moving our 300 pc's to Vista, and this is our test pc, so I
need to get this one right before we proceed.
I was wondering if it has to do with active directory?  We are planning to
move to active directory soon as well.
karonz - 28 May 2008 21:29 GMT
more info...
I have turned off the Firewall as we have our own.
I can access the folder structure on the primary domain controller, and its
backup, but can see none of the file sharing servers.  When I try, I am
prompted with a login box, and though I am logged onto the primary domain,
and authenticated with my administrator credentials, I put in the same
credentials in the authentication box and it tells me they are incorrect.
I have shared a folder on the Vista Pc and am able to see it from an xp
computer.

Windows IP Configuration

  Host Name . . . . . . . . . . . . : HORIZON
  Primary Dns Suffix  . . . . . . . :
  Node Type . . . . . . . . . . . . : Hybrid
  IP Routing Enabled. . . . . . . . : No
  WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Broadcom NetXtreme Gigabit Ethernet
  Physical Address. . . . . . . . . : 00-10-18-2E-F5-D1
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
  IPv4 Address. . . . . . . . . . . : 164.64.84.248(Preferred)
  Subnet Mask . . . . . . . . . . . : 255.255.255.0
  Default Gateway . . . . . . . . . : 164.64.84.1
                                      164.64.53.99
  DNS Servers . . . . . . . . . . . : 164.64.1.2
                                      164.64.3.5
  Primary WINS Server . . . . . . . : 164.64.84.5
  Secondary WINS Server . . . . . . : 164.64.53.10
  NetBIOS over Tcpip. . . . . . . . : Enabled

Tunnel adapter Local Area Connection* 6:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
  Physical Address. . . . . . . . . : 02-00-54-55-4E-01
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 7:

  Media State . . . . . . . . . . . : Media disconnected
  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Microsoft ISATAP Adapter
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes

Tunnel adapter Local Area Connection* 9:

  Connection-specific DNS Suffix  . :
  Description . . . . . . . . . . . : Microsoft 6to4 Adapter
  Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
  DHCP Enabled. . . . . . . . . . . : No
  Autoconfiguration Enabled . . . . : Yes
  IPv6 Address. . . . . . . . . . . : 2002:a440:54f8::a440:54f8(Preferred)
  Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301
  DNS Servers . . . . . . . . . . . : 164.64.1.2
                                      164.64.3.5
  NetBIOS over Tcpip. . . . . . . . : Disabled

> We have a network domain, all XP pro compters, though the domain controller
> is NT.  I have successfully joined this vista pc, and can 'see' all of the
[quoted text clipped - 10 lines]
> I was wondering if it has to do with active directory?  We are planning to
> move to active directory soon as well.
Robert L. (MS-MVP) - 29 May 2008 15:43 GMT
In Vista computer, do net view \\serveripaddress. Do you receive a system
error?

By the way, why do you use 164 IP?

Signature

Bob Lin, MS-MVP, MCSE & CNE
Networking, Internet, Routing, VPN Troubleshooting on
http://www.ChicagoTech.net
How to Setup Windows, Network, VPN & Remote Access on
http://www.HowToNetworking.com

> more info...
> I have turned off the Firewall as we have our own.
[quoted text clipped - 84 lines]
>> to
>> move to active directory soon as well.
karonz - 30 May 2008 14:34 GMT
Yes, I get system error 5, access is denied

I am using a 164 IP because that is the IP scheme for our network LAN

> In Vista computer, do net view \\serveripaddress. Do you receive a system
> error?
[quoted text clipped - 89 lines]
> >> to
> >> move to active directory soon as well.
karonz - 30 May 2008 21:15 GMT
I found the answer, it was in the Local Security Policies in the vista
machine. I had to change it to a lower setting to accomodate the NT domain.
thanks

http://www.vistaheads.com/forums/microsoft-public-windows-vista-administration-a
ccounts-passwords/68978-nt-4-domain-logon.html


> Yes, I get system error 5, access is denied
>
[quoted text clipped - 93 lines]
> > >> to
> > >> move to active directory soon as well.
 
Sign In
Join
My Latest Posts
My Monitored Threads
My Blog
My Photo Gallery
My Profile
My Homepage

Start New Thread
Enable EMail Alerts
Rate this Thread



©2008 Advenet LLC   Privacy Policy - Terms of Use
This website includes both content owned or controlled by Advenet as well as content owned or controlled by third parties.