Recommended Posts

not sure if it was answered or not, but adsl%20router is showing you a special character, in this case a space. for unix to like this, it needs " " around the path, or a backslash after asdl (asdl\ router). or alternativly you can remove that space from your asdl routers name. If other things are configured this can be problematic. Hope this helps you with future special characters. also remember Asdlrouter is different from asdlrouter in the unix world (caps matter, extensions don't)

 

I got owncloud installed on my freeBSD server and super easy to get working, but it was terrible at performing.. very buggy, froze the server up every time a file over 2MB was transferred. Good thing I made backups! Hope your ubuntu install goes better.

I don't think that is the correct syntax for smbclient, I would think you should have to escape \ so it would be like \\\\192.168.1.1

But I think you can just do something with -L and the IP.. it will throw out some errors but should work

budman@ubuntu:/$ smbclient -L 192.168.1.8
Enter budman's password:
Domain=[STORAGE] OS=[Windows Storage Server 2008 R2 Essentials 7601 Service Pack 1] Server=[Windows Storage Server 2008 R2 Essentials 6.1]

        Sharename       Type      Comment
        ---------       ----      -------
        ADMIN$          Disk      Remote Admin
        C$              Disk      Default share
        D$              Disk      Default share
        F$              Disk      Default share
        G$              Disk      Default share
        H$              Disk      Default share
        IPC$            IPC       Remote IPC
        J               Disk
        J$              Disk      Default share
        Media           Disk
        Molly           Disk
        Music           Disk
        temp            Disk
session request to 192.168.1.8 failed (Called name not present)
session request to 192 failed (Called name not present)
session request to *SMBSERVER failed (Called name not present)
NetBIOS over TCP disabled -- no workgroup available
budman@ubuntu:/$

thanks.. it worked with 

 /home/koshur# smbclient -L //192.168.1.1/segate -U admin
root@koshur-HP-ProBook-4530s:/home/koshur# smbclient -L //192.168.1.1/segate -U admin
Enter admin's password: 
Domain=[WORKGROUP] OS=[unix] Server=[samba 3.0.14a]
 
Sharename       Type      Comment
---------       ----      -------
segate(sda1)    Disk      
movies(sda1)    Disk      
IPC$            IPC       IPC Service (Samba Server)
ADMIN$          IPC       IPC Service (Samba Server)
Domain=[WORKGROUP] OS=[unix] Server=[samba 3.0.14a]
 
Server               Comment
---------            -------
ADSL ROUTER          Samba Server
KOSHUR-HP-PROBO      koshur-HP-ProBook-4530s server (Samba, Ubu
 
Workgroup            Master
---------            -------
WORKGROUP            KOSHUR-HP-PROBO
 

I'll try testing it for some time and decide if i should stick to it or not. 

 

Cheers!!

not sure if it was answered or not, but adsl%20router is showing you a special character, in this case a space. for unix to like this, it needs " " around the path, or a backslash after asdl (asdl\ router). or alternativly you can remove that space from your asdl routers name. If other things are configured this can be problematic. Hope this helps you with future special characters. also remember Asdlrouter is different from asdlrouter in the unix world (caps matter, extensions don't)

 

I got owncloud installed on my freeBSD server and super easy to get working, but it was terrible at performing.. very buggy, froze the server up every time a file over 2MB was transferred. Good thing I made backups! Hope your ubuntu install goes better.

 

Thanks for the tip. I'll put it to some testing and see how it tuns out on ubuntu

your listing with -L is messed up.. So in your screeny showing how you had it setup, you called your sharename segate, but then in your connection via smbclient it lists your shares as

Sharename       Type      Comment
---------       ----      -------
segate(sda1)    Disk      
movies(sda1)    Disk      
Where (sda1) is added to the sharename??

So far from what I can see the tp-link implementation of SAMBA is horrific! Seems you can not change the server name or workgroup name.. And it mangles what you create for a share name? That is terrible way to go about it, and seems it defaults to netbios name with a space in the name that you can not alter? Pathetic if you ask me.. Good luck with it, I can only assume its performance is par with what we have seen so far ;)

This topic is now closed to further replies.
  • Posts

    • Researchers claim Microsoft's quantum breakthrough is flawed by basic Python errors by Karthik Mudaliar Microsoft's aggressive roadmap to deliver a commercial quantum supercomputer by 2029 has now hit a bit of a snag, and it's not because of a complex sub-zero dilution refrigerator, but rather because of a few lines of basic Python code. A new critique published in the scientific journal Nature argues that simple software errors effectively manufactured the breakthrough that Microsoft's foundational research claimed back in 2025 into Majorana-based topological qubits. Topological quantum computing, the path that Microsoft chose for its research, relies on creating and controlling "Majorana zero modes." These are exotic quasiparticles that theoretically offer vastly superior error resistance compared to the highly sensitive superconducting qubits currently being championed by rivals like Google and IBM. However, physically proving you have created these particles requires sifting through massive amounts of complex electrical conductance data to isolate a specific "topological gap." Because of the sheer volume of data, physicists rely heavily on custom software pipelines to process the results. This is where the Python scripts come in. Now, according to the critique, Microsoft’s data processing software contained fundamental programming errors that ultimately skewed the published results. By mishandling data arrays or deploying incorrect logic within the Python script, the software supposedly discarded "noisy" or contradictory data. Which is why it only highlighted the specific electrical measurements that supported the topological-gap claim. The researchers behind the critique argued that this makes the findings invalid, suggesting the heralded "quantum leap" was actually a false positive generated by bad code and not a product of groundbreaking physics. However, Microsoft is pushing back hard against these allegations. The Redmond giant has formally rejected the criticism, saying that it's just a minor anomaly rather than a fatal flaw. According to the company, while there may have been a minor oversight in the data parsing scripts, it does not alter the fundamental reality of their physical experiment. Just weeks ago, Microsoft unveiled the Majorana 2 quantum processor, a milestone so significant that the company boldly accelerated its timeline for a commercial quantum supercomputer from 2035 down to 2029. But the new software allegations reopen an old wound. Microsoft's quantum division faced a remarkably similar crisis when a landmark 2018 paper on Majorana particles was famously retracted in 2021 after independent physicists discovered the data had been inappropriately cropped. That historical baggage makes the current Python-related allegations particularly sensitive. If the foundational math and data processing for the 2025 breakthrough are genuinely flawed, the highly anticipated 2029 commercial timeline could easily be delayed or, worse, cancelled.
    • Because of what they have done to VMware I will never buy anything Broadcom again.
    • AMD releases hotfix for driver install issues on Windows 10 PCs by Taras Buria Earlier this week, AMD released an important graphics driver update. Version 26.6.2 brought AMD FSR 4.1 support to the previous-gen Radeon lineup, the RX 7000 series, giving users better upscaling tech that was previously locked to the newest GPUs. However, the driver turned out to be a little buggy, with users reporting installation issues on systems still running Windows 10. AMD quickly acknowledged the bug and today released a hotfix to resolve the problem. The AMD 26.6.3 Hotfix update is now available for download from the official website. Given that it is a hotfix release, it has only one change in its release notes: AMD announced the update on its official X account and added that a WHQL driver update with the necessary fixes would be released next week. Meanwhile, users can apply the hotfix or roll back to the previous driver using the official AMD Cleanup Utility. You can download AMD Software: Adrenalin Edition 26.6.3 Hotfix Preview Driver from the official website here. It is compatible with all currently supported graphics cards and 64-bit Windows 10 and 11. Full release notes are available on the same page.
    • With Microsoft now listening to its core audience and acting upon received feedback, fans can finally expect a much better version of Windows 11 than what was available five years ago. Here is to five more years, Windows 11! I guess we all need a good laugh now and again...
  • Recent Achievements

    • Dedicated
      Scoobystu earned a badge
      Dedicated
    • First Post
      Tom Schmidt earned a badge
      First Post
    • One Month Later
      D0nn13 earned a badge
      One Month Later
    • Rookie
      +ChiefOfNeo went up a rank
      Rookie
    • One Year In
      Tom Schmidt earned a badge
      One Year In
  • Popular Contributors

    1. 1
      +primortal
      465
    2. 2
      +Edouard
      177
    3. 3
      PsYcHoKiLLa
      123
    4. 4
      Michael Scrip
      82
    5. 5
      Xenon
      76
  • Tell a friend

    Love Neowin? Tell a friend!