Recommended Posts

Hi all,

I am trying to share some files with my sister's computer. I am using Vista whereas she is using Windows XP.

I shared her folder and then i typed this on my vista computer " \\192.168.0.102 " and then it says that it is not accessible. You might nothave permission to use this network resource. Please contact the adminsitrator.

Why is this so ?

Link to comment
https://www.neowin.net/forum/topic/575002-help-with-home-network-please/
Share on other sites

did you configure file sharing on your firewalls? Are you running any firewalls other than XPs or any type of security software that might block file sharing.. virus scanners no do more than just scan files, etc.

Is she on XP home or Pro? What permissions did you setup on the share? on the file folder?

http://support.microsoft.com/kb/304040/

How to configure file sharing in Windows XP

Make sure you have File sharing enabled in Vista, I think it's not on by default...

It can be enabled through the control panel.... can't remember exactly. I once managed to get the file sharing work between XP and Vista, and the problem was just that sharing was not enabled in Vista. :)

Of course, make sure that any firewall isn't blocking connections.

Do you get a response from the other computer when pinging its IP address? (go to command prompt, and type "ping 192.168.0.102")

What kind of connection are you using? just ethernet-cable between the computers, or through a modem/router, etc?

  • 3 weeks later...

Well, I'd explain this.

Go to My Computer -> My shared folder -> Right click and then properties -> Sharing -> Tick all.

Restart.

Then let your sister go to My Network Places -> Entire Network -> 1 of these would have her PC. Make sure she does that too, try it and tell us what you get.

3) And also see KB922120 (this is probably the most important part of it though.
Most important part??? Nonsense -- having machines show up connected on the "Network Map" has absolutely NOTHING to do with accessing a file share - NOTHING!!

Thats like telling people that machines have to be in the same workgroup.. So this is going to be the new vista FUD on file sharing?

^ Sorry...:rolleyes:

But seriously, being able to see a computer helps a great deal.

Well, they have to be don't they?

NO! they freaking don't, a workgroup is nothing more than a place holder to where to put names in "browsing" Browsing has NOTHING to do with accessing a computer or its shares..

An you can see the computer JUST fine.. they just will not be connected on the total network map is all.

You will see them in the different workgroups if browsing, you can access them by name directly -- which is the fastest method

run \\computername

Seeing them with a Line drawn on your network map is nothing but eye candy - an has nothing to do with accessing shares on them.

If the user wants to see them in a pretty little map -- cause he can not figure out that his computers are all connected to his router ;) Then yes he needs to install that patch.. But it has NOTHING do with file sharing.

post-14624-1186575286_thumb.jpg

See all the machines on the network -- I can access shares just fine, I can see them just fine.. There is just not a line drawn on the map -- since they are not running the "Link-Layer Topology Discovery (LLTD) Responder" is all.

If you want, I put every single machine into a different "workgoup" and still be able to see them.. It will just take awhile for the browse list to correct it self.

Here you might learn something

http://www.microsoft.com/downloads/details...;displaylang=en

Computer Browsing for SOHO Networks with Microsoft Windows

Browsing has NOTHING to do with file sharing!

Here, this is what I am talking about.. As you can see now.. all the machines are in "different" workgroups. I can SEE them, I can access them!

An for grins I installed LLTD on one my xp machines.. You can see connected on the network map -- wooh hoow :rolleyes:

It can take a few minutes for the browse list to get into sync. (read the doc I linked too) the XP machines are in a xpgroup.. they will show up in a few minutes.

Even though the kids machine is not listed in the browse list yet.. Guess what I can still access it..

post-14624-1186580420.jpg

See the shared printer.

As I was saying the same workgroup has nothing to do with file sharing, nor does LLTD. So please do not spread FUD about that patch being need to share files between xp and vista.

I sometimes wonder how much use the ability to browse is?
IMHO its pretty much worthless.. Any user looking for a share, would they not know the name of the server the share is on?? ;)

It takes a lot longer to get anywhere.. it causes unnesessary chatter, etc.. etc..

If you use a share quite often, just put a shortcut to \\computername\share or map a drive letter to it, etc.

Only reason I let it even run on my network is to be able to answer questions, an post screen shots ;)

edit: I had to delete the map.. a tiny bit of personal info was on there ;) I can repost.. So we have a 50MB limit on attachments? Man, hmm maybe I should rethink how I put up screen shots if have to delete them in the future.. could make past threads a bit funny looking when found on a search.. Oh wait - no one searches here, so its all good ;)

here is the cleanedup map from the above post

post-14624-1186587788_thumb.jpg

Edited by BudMan

Just to be complete.. I told you the other machines would show up in a bit ;)

post-14624-1186591082.jpg

As you can see - all the machines are in different workgroups.. An they can be seen, an accessed ;)

Now please do not pass on any more FUD about that patch, or having to be in the same workgroup.

Vista an XP can share files just fine - there is no patches that have to be installed, nor anything special about workgroups that have to be configured, etc..

I have been trying to squash the workgroup FUD for years around here.. every time someone asks about file sharing it seems to rear its ugly head again.. We don't won't the same type of thing happening with LLTD. Thanks!

This topic is now closed to further replies.
  • Recently Browsing   0 members

    • No registered users viewing this page.
  • Posts

    • The actual download size is ~130–180 MB, not 100 MB.
    • Slight change of pace for me! Gunnar & the Grizzly Boys - Standard American (Official)  
    • draw.io Desktop 30.2.4 by Razvan Serea draw.io desktop is a downloadable security-first diagramming application that runs on Windows, MacOS and Linux. Creating diagrams in the desktop app doesn’t need an internet connection. This is useful when you are disconnected or when you must create diagrams in a highly secure environment, where data protection is of the utmost importance. When you use the draw.io desktop app, your diagrams will be stored on your local device. Because this is a stand-alone application, also designed to run offline, there are no interfaces to cloud storage platforms available. Of course, you can still store your diagrams in folders that are synchronised to your cloud storage if you wish. Easy-to-use diagram editor The draw.io apps work just like the office and drawing tools you are used to using. Drag and drop shapes from the shape libraries and drag to draw connectors between them. Drag connectors to add waypoints and set a precise shape and position, or let them reroute automatically. Double click and start typing to add a label to anything. Create tables and swimlane flows with a familiar tool. Style shapes and connectors with customisable palettes, sketch options, fonts and text formatting tools. Search for shapes, including in open-source icon libraries. Use our vast libraries of shapes and templates, organised into logical categories, to create a range of diagrams and infographics. Generate diagrams from text descriptions using our smart templates. Diagram faster with keyboard shortcuts. draw.io Desktop 30.2.4 changelog: Uses electron 42.4.1 Updates to draw.io core 30.2.4. Download: draw.io 64-bit | Standalone ~100.0 MB (Open Source) Download: draw.io 32-bit | ARM64 | ARM64 Standalone Links: draw.io Home Page | Project page @GitHub | Screenshot Get alerted to all of our Software updates on Twitter at @NeowinSoftware
    • Microsoft will soon allow some users to block Copilot from analyzing their Office files by Usama Jawad Microsoft Purview is a pretty useful data governance, security, and management service that allows customers to gain enhanced visibility and control over their content. It's meant for commercial customers, such as organizations that are storing data at scale. As AI continues to expand and infiltrate every corner of a firm, many are a bit conscious about the technology gaining access to their confidential data. Microsoft is now making a configuration change that will allow such customers to rest easy. Right now, users within an organization have the option to apply Purview sensitivity labels (when available) to secure certain files and label them as such. For example, if you apply the "Confidential" label on an Excel file, the file will be encrypted, and a "confidential" watermark will be applied to it. So, if this file is shared with anyone, they are aware that its access is supposed to be restricted. Up until now, Microsoft was allowing some connected experiences, like its AI services, to analyze files, regardless of their sensitivity label. This is of major concern to most organizations, as a recent example highlighted how confidential emails with data loss prevention (DLP) policies like privacy labels were being uploaded to Copilot for analysis. As such, Microsoft is updating an existing Purview data label sensitivity setting that prevents "some connected experiences that analyze content", from being blocked completely from doing this. The label isn't changing, but the blocking is now being enforced across all connected services (including Copilot and other AI tools), and now extends to Microsoft Word, Excel, and PowerPoint. Files with the label applied already will get this enhancement automatically too once it becomes available. Microsoft has urged IT admins to inform their respective helpdesk and compliance teams, update internal documentation, and review sensitivity labels to ensure that they meet their respective compliance needs. This change is tagged as MC1297982 in the Message Center. General availability is scheduled to begin in a phased manner soon and will complete by the end of next month. That said, it is important to note that this only applies to commercial customers who have a license that allows them to use Purview.
    • llamas are unruly going haywire in New Guinea.
  • Recent Achievements

    • Week One Done
      Eurosoft10 earned a badge
      Week One Done
    • One Month Later
      Eurosoft10 earned a badge
      One Month Later
    • One Year In
      Skeet Campbell earned a badge
      One Year In
    • One Month Later
      Sharbel earned a badge
      One Month Later
    • First Post
      BizSAR earned a badge
      First Post
  • Popular Contributors

    1. 1
      +primortal
      590
    2. 2
      +Edouard
      191
    3. 3
      PsYcHoKiLLa
      78
    4. 4
      Michael Scrip
      76
    5. 5
      neufuse
      73
  • Tell a friend

    Love Neowin? Tell a friend!