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

    • Qwen 3.6 is better value per dollar, and you can run it locally for free.
    • I don't believe them that anyone using threads, at least meaningfully. It's the same thing for Facebook, people just don't engage with Meta platforms like they are thinking. This isn't 2006.
    • Not taking AI slop on the go with me, hard pass for me.
    • Same Internet Archive seemed to grab the new version https://web.archive.org/web/20...d/Setup_MakeMKV_v1.18.4.exe Here's the link to an additional file it periodically downloads https://web.archive.org/web/20260213092148/https://www.makemkv.com/sdf.bin I think update's keys, etc. To manually trigger this update, put the sdf.bin file in the root of where the program is installed. When you launch the program it will pick up the file and import it. Typically put it here: C:\Program Files (x86)\MakeMKV\sdf.bin
    • Windows 11 KB5094126, KB5093998 bugging out Office apps but it may not be Microsoft's fault by Sayan Sen Microsoft last week released Windows 11 KB5094126 and KB5093998 as the latest Patch Tuesday updates. Following that the company also published the accompanying dynamic updates under KB5094149, KB5095971, and KB5094156. Although the tech giant did not acknowledge any major problems, some users online reported various issues ranging from OneDrive and Dropbox access problems, BitLocker recovery lockouts, to blue screens and BSODs. You can read about them in this dedicated piece. While there is still no confirmation about those problems from Microsoft the company has admitted to another bug which we did not report on. The tech giant has confirmed it has received reports of an issue in which certain third-party applications may be unable to launch Microsoft Office apps or open Office documents after installing the Patch Tuesday. This affects both Windows 11 as well as Windows 10. The company says the problem impacts a subset of applications that rely on OLE (Object Linking and Embedding) automation to communicate with Microsoft Office programs. According to Microsoft, affected scenarios involve third-party software attempting to open Office applications or documents from within their own interface. In such cases, the Office program may fail to launch altogether, or the requested document may not open. Oddly there may not be any error message, which probably makes the issue difficult to diagnose. The bug affects several Office products, including Word, Excel, PowerPoint, Access, and other apps in the Microsoft Office suite when they are launched through the affected software. These include tax and accounting software such as CCH Engagement and Workpaper Manager, dental practice management solutions like Dentrix and Softdent, as well as the popular research and reference management tool Zotero. Microsoft adds that other applications using similar Office integration methods could also experience the same problematic behavior. To understand the issue it is important to look at OLE, the Microsoft technology involved. OLE allows different applications to work together and share data, while its Automation feature lets one program control another. Thus this enables third-party software to launch Microsoft Office apps, open documents, and perform tasks automatically without requiring users to switch between programs. Because many accounting, healthcare, research, and business applications rely on OLE automation to interact with Word, Excel, PowerPoint, and other Office apps, any disruption can break those workflows. As a result, affected software may be unable to open Office documents or launch Office applications even though the programs themselves continue to work normally. At the moment the company has not provided a permanent fix though it has confirmed that engineers are actively working on a resolution, which will be delivered through a future Windows update. As such additional details will be shared once more information becomes available. In the meantime, Microsoft recommends a simple workaround for affected users whic is to open the Office application or document directly rather than launching it through the third-party program. For enterprise customers and organizations managing larger deployments, Microsoft says an additional mitigation is available. Admins experiencing the problem on their managed devices are advised to contact Microsoft Support for business to obtain and apply the workaround.
  • Recent Achievements

    • Reacting Well
      Dys Topia earned a badge
      Reacting Well
    • Conversation Starter
      NovaEdgeX earned a badge
      Conversation Starter
    • One Year In
      Console General earned a badge
      One Year In
    • Week One Done
      Twozo Technologies earned a badge
      Week One Done
    • One Month Later
      Twozo Technologies earned a badge
      One Month Later
  • Popular Contributors

    1. 1
      +primortal
      517
    2. 2
      +Edouard
      184
    3. 3
      PsYcHoKiLLa
      106
    4. 4
      Steven P.
      88
    5. 5
      ATLien_0
      68
  • Tell a friend

    Love Neowin? Tell a friend!