Touch the Future Now at Staples
Networking & wireless: XP Home: The specified network name is no longer available
No joy so far
by Jack Yan - 4/16/05 4:11 AM In reply to: Problem arose after Windows update by Jack YanI've tried others' suggestions above where applicable, and still no joy. I've rolled back the update and can't get the two machines to talk to one another. All three errors are present: the network name one, the path too deep one, and the semaphore one.
The wires are all direct, not cross-overs; not sure if I can tell you much more about the set-up. Pings work.
I'd welcome any clues.
TIA,
Jack
Works with Remote Desktop (?)
by Teramedia - 11/6/07 8:13 AM In reply to: No joy so far by Jack YanI have a wifi connection from a laptop to a router, which goes to a switch, which then goes to a desktop HTPC. Recently, I began to see the same message everyone else is getting when I try to transfer large files.
The weird thing is, if I first establish a remote desktop connection from the laptop to the desktop, then the file transfers seem to work somewhat better. I am sometimes able to transfer the file using this approach.
the specified?
by Rickleisin - 11/18/07 6:04 PM In reply to: Works with Remote Desktop (?) by Teramediaok, as with all the other sites and forums and this loss of the specified network, my wireless system was losing connection. The fact that i had fast drives on one faster machine uploading to slower machine and drive that was primary, also a slower drive, was why all that was happening. The drive in question is jumpered as slave but i have it booting primary. I returned back up os/drive to the primary boot in bios, that corrected everything. The task before me now is to pull both drives from machine and set Jumpers for the master and slave, and boot them accordingly. Not visa versa
Solved it unconventionally
by Jack Yan - 11/29/08 7:04 PM In reply to: Works with Remote Desktop (?) by TeramediaTeramedia, I only saw your post today after I had the same error recur. Did you manage to fix your problem? I posted my fix soon after (back in 2005) and was able to use the same solution this time around.
Fixed, after two days!
by Jack Yan - 4/17/05 2:36 AM In reply to: XP Home: The specified network name is no longer available by GooballHi guys:
D-Link tech support was great but their solution was to exchange the unit. I eventually plugged in my laptop and it worked, so I concluded it had to be a set-up thing between Desktop Computer A and Desktop Computer B, both running XP Home.
I began investigating all the settings again, and strangely, the laptop and computer A (which could talk to one another) had different things installed under 'This connection uses the following items'—contrary to the advice I had read. So I knew that the differences would not be a major problem.
Anyway, I went to Configure the network card on B and a message came up saying that if I went in, some of my new settings would disappear. This didn't happen with either A or the laptop, so I knew something was up.
The laptop and the B have the same family of network card, yet under the 'Advanced' tab, the laptop had 'Link Speed/Duplex Mode' on 'Automatic' (which is what B was set to).
However, after I set B to '10 Full Mode' ('10 Half Mode' also worked), I could do everything!
Just for clarity, A has a different type of network card and only has 'Line Speed' as the sole property under 'Advanced'. It's set on 'TP Half Duplex'.
So there you have it: I went _against_ all the rules, have totally different settings between the machines, and it all works!
Regards,
Jack
www.jackyan.com
Thank goodness for CNet
by Jack Yan - 11/29/08 7:02 PM In reply to: Fixed, after two days! by Jack YanI came across the same error message today after a formatting and reinstallation last week—thank goodness CNet has kept these pages online. Saved a lot of time. If anyone from CNet is reading this, thank you.
The specified network name is no longer available/IIS
by Infohold - 9/25/06 2:05 PM In reply to: XP Home: The specified network name is no longer available by GooballI'm getting the same error from IIS 5.0 (On Win2K Pro Box) when users try to download large files. I havn't yet found the root of the problem, but I'd like to point out that this box has the exact same NIC (SiS 900 PCI Fast Ethernet Adapter). It's using the SiS Driver, V 1.16.1.0. This problem has just began occuring recently...
| Forum legend: | |
 |
Locked thread |
 |
Moderator |
 |
CNET staff |
 |
Samsung staff |
 |
Norton Authorized Support team |
 |
AVG staff |
 |
Windows Outreach team |
 |
Dell staff |
 |
Intel staff |
