File and Folder Sharing Problems
I have upgrade installed Vista RC1 build 5600 onto XP pro SP2 I cannot get the network sorted out - and need some help I have a workgroup: 1 Vista machine and 1 laptop running XP Professional SP2, both connected wirelessly via a 3com ADSL modem router I have shared files and folders on the Vista PC network discovery on file sharing on, public folder sharing on, printer sharing on. password protection off, media sharing on. On the XP PC I have sharing on, for everyone. I can see both computers in the workgroup on both PCs I can open shared files on the XP PC from the Vista, but cannot save. I cannot open folders on the Vista PC form the XP; sometmes it asks for username /password which I enter but it does not accept, then I get 'not accessible' message I have a shared printer on the Vista PC which I cannot access over the network. Please advise any troubleshooting steps thanks John
September 29th, 2006 4:36pm

HI John I have EXACTLY the same issue. I have tried switching the Vista Firewall off, (domain, public and private) to no avail. Have you come across an answer perhaps ? T
Free Windows Admin Tool Kit Click here and download it now
October 4th, 2006 9:27pm

Did you let the Connect to a Network Wizard to discover your network? Wizard to find most proper options satisfy your networking needs due to new TCP/IP stack. Good luck
October 4th, 2006 10:18pm

Thanks for your reply No, not specifically - the netork was discovered and connected to automatically. I have just disconnected and reconnected to the router connection - no change still the same behaviour. Is this what you mean for me to try? Network connection is definately there - I can see the computers and ping them ok - so it must be a protocol issue I guess. Can you enlighten me on what you mean by new tcp/ip stack? I have attached belowthe network details in case you can see anything there: (some details XXed out) Connection-specific DNS Suffix: Description: Broadcom 802.11g Network AdapterPhysical Address: XX-11-50-XX-7ADHCP Enabled: YesIPv4 IP Address: 192.168.XX.3IPv4 Subnet Mask: 255.255.255.0Lease Obtained: 04 October 2006 10:09:24Lease Expires: 05 October 2006 08:52:09IPv4 Default Gateway: 192.168.XX.1IPv4 DHCP Server: 192.168.XX.1IPv4 DNS Server: 192.168.XX.1IPv4 WINS Server: NetBIOS over Tcpip Enabled: YesLink-local IPv6 Address: XXXX::849a:8f9a:87a2:f412%7IPv6 Default Gateway: IPv6 DNS Server: Am I meant to be on IPv6 on Vista? The other thing I saw on trawling the forums is that it may be a router/hardware issue. I am using a 3Com OfficeConnect ADSL Wireless 11g Firewall Router,I cannot find anyknown issues. many thanks for any more guidance John
Free Windows Admin Tool Kit Click here and download it now
October 4th, 2006 11:13pm

Hi Trevor I am glad I'm not alone, but sorry for your troubles! no - no luck as yet - see later posts are you on a wireless or wired network? (I wonder if that is a factor?) I would try a wired netowk and a different router - but my desktop has no network card but the wireless. I might borrow another wireless router just to see if this makes any difference Let me know if yo have any success John
October 4th, 2006 11:16pm

I have done some more tests and here are the results I changed the workgroup name on both computers and (after restart) now have full access to files & folders on the XP pro computer from the Vista PC. I can open, amend save and create; so all is well there. On the XP pro PC I can see the Vista PC listed on workgroup computers and can pingit. I cannot access it - I get asked for the username & password and when I enter it - eithera the local computer user or a Vista computer user I get 'access is denied' message. Any suggestions? John
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2006 12:45am

In Vista, it's not a must to have IPv6, for example, if it doesn't work, you get Limited Connectivity for IPv6 and that won't affect your network. The following are the new features of the Next Generation TCP/IP stack "Source: http://tinyurl.com/dkklc ": Dual IP layer architecture for IPv6 The implementation of IPv6 in Windows XP and Windows Server 2003 is a dual stack architecture. For IPv6 support, you have to install a separate protocol through the Network Connections folder. The separate IPv6 protocol stack had its own Transport layer that included Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) and its own Framing layer. Changes to protocols in either the Transport or Framing layers had to be done to two Windows drivers; Tcpip.sys for the IPv4 protocol stack and Tcpip6.sys for the IPv6 protocol stack. The Next Generation TCP/IP stack supports the dual IP layer architecture in which the IPv4 and IPv6 implementations share common Transport and Framing layers. The Next Generation TCP/IP stack has both IPv4 and IPv6 enabled by default. There is no need to install a separate component to obtain IPv6 support. Easier kernel mode network programming The Next Generation TCP/IP stack supports Winsock Kernel (WSK). WSK is a new transport-independent kernel mode Network Programming Interface (NPI) for Transport Driver Interface (TDI) clients. Using WSK, kernel-mode software modules can perform network communication using socket-like programming semantics similar to those supported in the user-mode Windows Sockets 2 API. While TDI is supported in Windows Vista for backward compatibility, TDI clients should be updated to use WSK to achieve the best performance. Support for a strong host model When a unicast packet arrives at a host, IP must determine whether the packet is locally destined (its destination matches an address that is assigned to an interface of the host). IP implementations that follow a weak host model accept any locally destined packet, regardless of the interface on which the packet was received. IP implementations that follow the strong host model only accept locally destined packets if the destination address in the packet matches an address assigned to the interface on which the packet was received. The current IPv4 implementation in Windows XP and Windows Server 2003 uses the weak host model. The Next Generation TCP/IP stack supports the strong host model for both IPv4 and IPv6 and is configured to use it by default. You can configure the Next Generation TCP/IP stack to use a weak host model. The weak host model provides better network connectivity. However, it also makes hosts susceptible to multihome-based network attacks. New security and packet filtering APIs The interfaces in the current TCP/IP stack for TCP/IP security (filtering for local host traffic), the firewall hook, the filter hook, and the storage of packet filter information has been replaced with a new framework known as the Windows Filtering Platform (WFP). WFP provides filtering capability at all layers of the TCP/IP protocol stack. WFP is more secure, integrated in the stack, and much easier for independent software vendors (ISVs) to build drivers, services, and applications that must filter, analyze, or modify TCP/IP traffic. New mechanisms for protocol stack offload The Next Generation TCP/IP stack can offload the processing of TCP and other types of traffic to Network Driver Interface Specification (NDIS) miniport drivers and network interface adapters. Offloading TCP and other protocol processing can improve performance for high-bandwidth networks or high-volume servers. New support for scaling on multi-processor computers The architecture of NDIS 5.1 and earlier versions limits receive protocol processing to a single processor. This limitation can inhibit scaling to large volumes of network traffic on a multi-processor computer. Receive-side Scaling resolves this issue by allowing the network load from a network adapter to be balanced across multiple processors. New extensibility The Next-Generation TCP/IP stack has an infrastructure to enable more modular components that can be dynamically inserted and removed. Reconfiguration without having to restart the computer The Next-Generation TCP/IP stack uses a new method to store configuration settings that enables more dynamic control and does not require a computer restart after settings are changed. Automatic configuration of stack settings based on different network environments The Next-Generation TCP/IP stack automatically senses the network environment and adjusts key performance settings, such as the TCP receive window. Improved stack auto-tuning and configuration reduces the need for manual configuration of TCP/IP settings. Supportability enhancements There is extensive support for run-time diagnostics, including support for TCP Management Information Base (MIB)-II and better system event logging and tracing. The following features are improvements in the Next Generation TCP/IP stack: Better support for computers that roam between networks. Better support for developers of multicast-enabled applications and networks. TCP performance enhancements for high-speed networks, asymmetric satellite links, and wireless and other high loss networks. Improved portability of the Next Generation TCP/IP stack to other Microsoft operating systems such as Windows CE, Xbox, and Windows Embedded. Improved resistance against all known TCP/IP-based denial of service and other types of network attacks.
October 5th, 2006 2:39am

Thanks Ahmad That information is helpful and now I know that IPv6 is not an issue I do use the XP machine fro my work, and take it to different workgroup and domain environments. I have not had a problem re-establishing connection with my 'home' workgroup before. but are there issues here that I should be looking at? Ihave made some attempts to start the network connections from scratch in the hope that settings will be correctly configured by createing a new workgroup on both machines with some inprovement- see posts above. I have full network sharing now from the Vista PC to the XP one. But seem to have lost access from the XP PC to the Vista - connectivity is still there OK Do I need to clear or reset the IP connections? (I'm not sure of the correct terminology here) thanks John
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2006 3:05am

Try to configure IPs manually (NOT via DHCP). Static IPs may work fine for you. Just don't make duplication of IPs. Good luck
October 5th, 2006 1:08pm

Hello Ahmad no I'm afraid manually configuring made no difference. I reconfigured both PC's and the router and rebooted all of them. Internet and what network connections I had were fine - but no luck accessing the Vista machine from the XP; although I am back now to being able to see the 'My Documents' folder which is one but not the only shared folder. This and its subfoldersshow no files (although they are there) Should I be looking at the WINS or NETBIOS settings? thanks for your advice John
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2006 8:02pm

I'm afraid to say, but try doing ActiveDirectory or confiuge DNS server..not sure! Good luck
October 5th, 2006 8:37pm

Ok thanks will give that a go another piece of information that may help the diagnosis? I have a folder on the Vista PC syncrhonised on the XP PC, needless to say, It will not synchronise, although it says it is ready for it. When I go to synchronise, I am asked for username & password, it will not accept any local one from either computer, but I am getting the error: Unable to connect to \\... multiple connections to a server or a shared resource by the same user, using more than one user name, are not allowed. Disconnect all previous connections to the server or shared resource and try again I don't know how to 'disconnect'! does this point to something you recognise? many thanks John
Free Windows Admin Tool Kit Click here and download it now
October 5th, 2006 10:37pm

For what it's worth I have the same problem - although... I have two XP Laptops and one can see the Workgroup and Printer while the other can't! Both have worked at times! I once got prompted for a password and it worked fine. Never worked again! Aaaargh!
October 17th, 2006 8:17am

Thanks for your post! glad it's not just me, I am in pretty much the same boat as before I am interested that you say sometimes it works. I have had differing behaviour atvarious times - makes it all the harder to pin down what it is! Ihave total transparency when looking from the Vista machine at the XP machine, but next to nothing the other way around As I said in my last post, the XP machine sees the Vista one, and thinks that it is ready to synchronise, but no luck (password not accepted)I cannot see the printer folder at all I have reported this via the Microsoft Beta Client, but have had no reply or acknowledgement. Does anyone have any further troubleshooting steps please? thanks John
Free Windows Admin Tool Kit Click here and download it now
October 17th, 2006 1:15pm

Windows Vista RTM will be released by 2 weeks (and Office 2007 too), I think all these bugs would be fixed there, prepare to purchase it if you would like deploying it. Good luck
October 17th, 2006 8:42pm

Thanks Ahmad OK I guessI can wait just for clarification please, is Vista RTM available as a download as well, how (or will I ) do I get notification Do I have to purchase this one? many thanks John
Free Windows Admin Tool Kit Click here and download it now
October 17th, 2006 9:25pm

Network problems 'disappeared'! I was working on the XP computer over VPN this morning at a remote site, when I logged off, the offline syncronisation icon said that my workgroup computer was available for reconnect - as it has before, but this time sync was done perfectly - no request for password or anything. I then looked in printers & faxes the printer was there - no need to search for it, test page printed perfectly. And, all shared files and folders on the Vista computer are accessible from the XP one. It took a couple of reboots to see the XP files from the Vista machine (that was OK before!) So I'm not sure whether this is a fix or a glitch! I did turn the XP firewall off and on, maybe it was that? I did not change any settings. I have made no other changes that I am aware of - I note Ahmed's comments above - I guessmy 'discovery'is just for information but worth a shot John
October 19th, 2006 3:50pm

I can connect to my printer on another XP machine on my workgroup but when I print everything comes out printed in reverse! It's like it's trying to print hebrew! Reading from right to left! lolI have an HP Deskjet 5740If I remove and add the printer a couple of times it seems to fix it!Very strange!
Free Windows Admin Tool Kit Click here and download it now
October 24th, 2006 12:15am

This is a common problem with users adding a Vista machine onto a network with one or more XP pcs. The solution is found by making a very simple (although aloof) choice when going through the steps of sharing a folder (such as "Documents") in Vista. This important step is: -ensure that you choose the option "Guest" (not Everyone) and then once added, make sure you set the Permission Level to "Co-Owner". (Most users mistakenly choose "Everyone but that choice only applies to people or groupson a list which is another type of function and I wont cover that here.) Also, after you have gone through the steps to share a folder, do the following: 1. Right-click the folder you want to share and choose Properties 2. Choose the Sharing tab and then click the Advanced Sharing button 3. Ensure there is a checkmark in the "Share this folder" option 4. Then click the Permissions button below 5. In the Permissions for Everyone option, select the appropriate level (you will probably want to choose Full Control in order to have complete access over the network) 6. Choose OK 7. Choose OK 8. Choose Close That should do it.
November 21st, 2007 8:28pm

This topic is archived. No further replies will be accepted.

Other recent topics Other recent topics