Recommended Posts

Hmmm, I'm stumped with this one...

I have a couple of XP machines on my network. Both are configured to be visible on my network and I've had no problems accessing them from Vista or any of the Windows 7 builds up to the newly leaked 7057.

Having installed 7057 (fresh install) neither of my XP machines are visible. Normally I can just click on the Network icon in Windows 7 and they appear.

Naturally I've checked all the relevant settings that I can think of but normally the only setting I have to adjust is the Workgroup name.

I noticed an option to alter file sharing encryption settings to 128bit or 40/56bit. What does XP use? I wondered if perhaps (by default) it uses no encryption at all and that's what causing all the problems. Note that I do not use a wireless connection as I have a wired LAN.

All I need is one way access to the XP machines. I've never had any problems with this before. It has always "just worked" out of the box. If it's a bug then I'll be forced back to an older build.

Has anyone managed to network build 7057 to another PC running XP? Any other suggestions that might help? Thanks in advance.

Edited by wiggly1uk2000
Link to comment
https://www.neowin.net/forum/topic/746192-networking-issue-with-build-7057-x86/
Share on other sites

Given that I'm using a wired (not wireless) LAN, where would I find encryption settings on my XP machines?

I meant this

post-62693-1237076745.png

Found here : Control Panel\Network and Internet\Network and Sharing Center\Advanced sharing settings

I meant this

post-62693-1237076745.png

Found here : Control Panel\Network and Internet\Network and Sharing Center\Advanced sharing settings

That has no bearing on this bug dhan. The 7057 build definitely has a problem networking with XP. It connects but shows no icon(s) for the XP machine(s) in the Network window. The only way you can browse the network is by typing in the path manually. Changing encryption settings makes no difference to this.

Roll on RC.

Edited by wiggly1uk2000
  • 2 weeks later...

I'm actually having a reverse problem: I'm trying to share a folder on my Windows 7 machine. No problems with Vista. XP (SP3) sees the folder but can't access it ("insufficient privileges" or something like that). I've tried all sorts of variations on net use, nothing. Any ideas?

I'm actually having a reverse problem: I'm trying to share a folder on my Windows 7 machine. No problems with Vista. XP (SP3) sees the folder but can't access it ("insufficient privileges" or something like that). I've tried all sorts of variations on net use, nothing. Any ideas?

choose "turn off password protected sharing" in advanced sharing settings for that network type you are using.

choose "turn off password protected sharing" in advanced sharing settings for that network type you are using.

It's been off. Still doesn't work. I'm wondering how mature this build really is - the desktop.ini coming up in notepad right off the bat would indicate half-baked at best. I know it says RC1 when you install it but this is a leaked build, hardly believe they really meant this to be the RC

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

    • No registered users viewing this page.
  • Posts

    • I bought one of these last year. I really hope I won't have to deal with this crap. My drive is in good condition at the moment.
    • Umm, read my answer again! If you have something to add or contribute, feel free. Otherwise my point was that you apparently dont want faster updates... so you want slower updates by process of elimination. If you have something to contribute, meaningful answers are better.
    • These features described above are good, but far from what developers will like the most. The main feature that developers will care and love the most it's called "Bring Your Own Models". It gives us the ability to connect to LOCAL AI models running on Ollama. The feature it's located on GitHub Copilot tab -> On the model picker where you can select "manage models" instead of paid models and then it will show you the "Bring your own models" window where you can now select Ollama and the endpoint of your local server. So if you have a beefy spec machine you can now use your own model 100% local inside Visual Studio 2026 18.7.0
    • Microsoft Teams is getting a controversial location tracking feature that users may hate by Usama Jawad Image generated with Microsoft Copilot Earlier this year, Microsoft planned to roll out a controversial location tracking feature in Teams, but following customer feedback, it decided to delay its release. The bad news is that the company has decided to launch it later this year, but it's based on roughly the same design that was shared earlier, which means that many users still have good reason to worry. Basically, Microsoft Places and Teams have received workplace check-ins via Wi-Fi. The idea is that if an employee arrives at the office and connects to their enterprise network, their profile status indicator will show them as being present in the office. For example, if you arrive at work, open Teams on your PC, and connect to the "Studio B" company Wi-Fi network, your Teams profile will indicate that you are present in "Studio B", as shown below: Microsoft says that this feature is basically a replacement for physical workplace check-in peripherals, it reduces the need to manually update your status, and it also enables co-workers to know that you're at work so that they can coordinate in-person meetings with you. IT admins can enable this workplace check-in capability at a tenant level, and users have the ability to control whether they want to enable it or not. Of course, all of that sounds great on paper, but naturally, many Teams customers may still have concerns, as they did before. This is because it enables your reporting manager and other members of the organization to track if you are at the office, when you arrive at the office, and where you are right now. This could be problematic for people who work in what they consider to be flexible work environments or hybrid setups, and this kind of location tracking could be considered an invasion of privacy. Microsoft has tried to alleviate some of these concerns by letting users know that they can manually set their location easily, which essentially overrides workplace check-in if they feel uncomfortable with it. However, that doesn't really solve the problem because your organization could enforce a workplace policy that mandates that this feature remains enabled. The Redmond tech giant has also assured users that this capability does not store historical data and is only a real-time indicator of location. Finally, it only generates a signal when you connect to a corporate network, which means that if you are working from home and connect your PC to your personal Wi-Fi, it won't broadcast your location to your employer; you will simply be shown as "Remote". Microsoft has encouraged IT admins to prepare for this change and begin informing users so they know what to expect once it begins rolling out later this year.
  • Recent Achievements

    • Very Popular
      AndrewSteel earned a badge
      Very Popular
    • Veteran
      Taliseian went up a rank
      Veteran
    • One Month Later
      Clizby earned a badge
      One Month Later
    • One Month Later
      Timaximus earned a badge
      One Month Later
    • Week One Done
      Timaximus earned a badge
      Week One Done
  • Popular Contributors

    1. 1
      +primortal
      516
    2. 2
      +Edouard
      162
    3. 3
      PsYcHoKiLLa
      157
    4. 4
      Steven P.
      82
    5. 5
      ATLien_0
      81
  • Tell a friend

    Love Neowin? Tell a friend!