Question Locked

How to restore Microsoft Windows Network in XP Home?

0 helpful
70 replies
Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

I want to network my laptop and desktop computers together so I can share files and printers. I have a crossover cable connecting the two. The desktop computer runs XP Home w/SP3; the laptop runs XP Pro w/SP3. I used the Network Setup Wizard on both systems to establish a workgroup connection, called MSHOME. I can ping each of the machines, regardless of which machine I'm on.

The problem is, when I go to the desktop, I can't see its own shared folders or printers, and "View Workgroup Computers" is empty. I traced this to a missing "Microsoft Windows Network" icon under "Entire Network". I've tried several things to restore this, including removing SP3, reinstalling Windows, and reinstalling SP3. But that didn't work.

I'm stumped. I'd rather not have to resort to thumb drives to move files across the machines.

70 replies

by thumbsup2

.... It's not designed for networking. That component isn't included in the HOME version.

by rob miners

How to set up a small network with Windows XP Home Edition (PART 1)

http://support.microsoft.com/kb/813936/en-us

Keep us informed as to your progress if you require further assistance.

If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. ;) :D

by thumbsup2

When did they add that? Sp2? I haven't seen one, personally, but I was told that Home didn't support networking. :0

by rob miners

bwilmot is right though it is not supported on a Domain but you can still use it to access shares or surf the net. It also seems to work better if you put it into a Workgroup. Users seem to have more problems with Home as opposed to XP Pro because of it's limitations. ;)

< too many t's >

by jim.poltrone

I've seen those pages before. Unfortunately, I couldn't find anything in any of the 8 parts that would solve my problem. I can't even run \\orac (my desktop computer's name) at the command prompt; I get "The network path was not found.

I tried running X-Setup 6.6 which listed my machine name as my domain name. I cleared it out, restarted, and when I entered X-Setup again, the domain name was still there.

by rob miners

the steps that you have taken by following this setup.

http://www.5starsupport.com/tutorial/networking-crossover-cable.htm

Keep us informed as to your progress if you require further assistance.

If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. ;) :D

by jim.poltrone

I tried the settings as suggested in the "How To Set Up File Sharing in Windows 2000/XP Pro" document, and I still can't see my own computer or shared documents in My Network Places. I can see them when I look at Management Console, though.

There's probably a registry hack I need, or I need to register (or re-register) some of the DLLs.

by rob miners

click on Start, Run and type cmd and press Enter.

Type ipconfig /all> c:\ip1.txt and press Enter.

On the second PC Type ipconfig /all> c:\ip2.txt and press Enter.

Post the contents of both files for us to have a look at. If you have followed the instructions that have been provided you should have a connection.

by jim.poltrone

As you suggested, I followed the instructions in the website you provided. (Question: Should I be using 192.198.0.x or 192.168.0.x?) Do I also need to specify a gateway address?

I also commented out the entries I had in C:\windows\system32\drivers\etc\hosts. I remember having to make entries to that file on my work machine. But maybe I'm confusing domain with workgroup.

I'm currently able to ping my systems. But when I open up My Network Places on my desktop computer, I still don't see my shared folders. And when I click on View Network Computers, I see nothing.

I uninstalled and reinstalled File and Printer Sharing for Microsoft Networks, which had no effect. I also followed the instructions in Microsoft Knowledge Base article #318030, which also had no effect. I unshared and reshared my folders and printers, which also had no effect. :(

Some history: I used to have a working network when I was running Windows 98. I had a hub between the desktop and a different laptop. I upgraded to XP Home in April 2007. (I didn't want to spend the extra $100 for the XP Pro upgrade.) I upgraded the laptop in May 2008. In June 2008, I tried installing a wireless router so I could network with the desktop from my laptop. (I use a dial-up connection to get to the Internet.) But the router setup didn't allow me to do this. Instead of going back to the hub, I went with a crossover cable.

Thanks for sticking with me.

by rob miners

Be sure that both computers are logged in to Windows with an Account on each with the same Logon ID and a password.
Connect each end of the cat5 crossover cables in to the network cards of each computer.

In order for both PC's to be able to communicate together, the Ethernet adapters will need to be configured with a static IP address and a common Subnet mask. As an example, assign one PC an IP address of 192.168.0.1 and assign the second PC an IP address of 192.168.0.2. Both machines should use the Subnet mask 255.255.255.0. Here's how to configure your Network Card: Go to Start, Control Panel, Network Connections and right click your Local Area Connection and select Properties. Scroll the list for the entry titled: Internet Protocol (TCP/IP). Click the entry and select Properties. Under the General tab, tick the box titled: Use the following IP address. Enter the IP address and Subnet mask that you would like to use. While you are ther check that File and Print Sharing has a tick in the box.

Repeat the steps above for the second computer system.
Be sure that both PC's have a common workgroup name of 15 characters or less. I prefer to use the name workgroup.

Here's how: Go to Start, Control Panel and System. Select the Computer Name tab. Click the Change button. Change the Workgroup name. Repeat these instructions on the second computer ensuring that both computers are named exactly the same. IE WORKGROUP.
Reboot both computer systems.

Next, open a command prompt on one of the computers by going to Start,Run and Type in cmd and press Enter or click OK.

Type in ping 192.168.0.2 (if you are using the computer assigned with 192.168.0.01) press Enter.
Four TTL replies to your ping should be indicated. eg:TTL=128

Note: If you receive a "timed out" message when attempting to ping your selected IP address. It is possible that the Internet Connection Firewall is interfering. Try right clicking on "My Network Places", then select Properties. Right click your Local Area Connection and select Properties once again. Click the Advanced tab. Click Settings, Exceptions and check to ensure that File and Printer Sharing, Remote Assistance and Remote Desktop have a Tick in the box.

Keep us informed as to your progress if you require further assistance.

If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. ;) :D

by jim.poltrone

>While you are ther check that File and Print Sharing has a tick in the box.

I'm not seeing this box. I have only two checkboxes at the bottom of this screen: Show icon in notification area... (which is checked), and Notify me when this connection has limited or no connectivity. (Is there a way I can send you a screenshot of this?)

File and Printer Sharing for Microsoft networks is installed on this connection. Shall I uninstall and reinstall this?

by rob miners

On the Generals tab above where you are looking at those two boxes you should see a small title. This connection uses the following items: Below that you should see Client for Microsoft Networks with a box to the left of it. If Client for Microsoft Networks is not there you will have to add it by clicking Install, select client and click Add. Select it from the list and click OK. File and Printer Sharing for Microsoft Networks should be below that and the box checked. If it is not there click the Install button.

Now select Service from the list of component types and click OK.

On the next screen select File and Printer Sharing for Microsoft Networks and click OK.

File and Printer Sharing for Microsoft Networks should now be added to the list. click Ok to exit.

Screen shots here:

http://www.wellesley.edu/Computing/FileSharing/Windows/win2kxp.html

Keep us informed as to your progress if you require further assistance.

If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. ;) :D

by jim.poltrone

===== From the desktop computer (while logged in to my ISP):

Windows IP Configuration

Host Name . . . . . . . . . . . . : orac

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter WORKGROUP:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : SiS 900 PCI Fast Ethernet Adapter

Physical Address. . . . . . . . . : 00-40-33-E0-81-2A

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.0.1

Subnet Mask . . . . . . . . . . . : 255.255.255.0

IP Address. . . . . . . . . . . . : fe80::240:33ff:fee0:812a%4

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

PPP adapter Fuse.net:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : WAN (PPP/SLIP) Interface

Physical Address. . . . . . . . . : 00-53-45-00-00-00

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 216.68.113.73

Subnet Mask . . . . . . . . . . . : 255.255.255.255

Default Gateway . . . . . . . . . : 216.68.113.73

DNS Servers . . . . . . . . . . . : 216.68.1.100

216.68.2.100

Tunnel adapter Teredo Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : 80-00-FB-5A-27-BB-8E-B6

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::ffff:ffff:fffd%5

Default Gateway . . . . . . . . . :

NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter 6to4 Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : 6to4 Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : D8-44-71-49

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 2002:d844:7149::d844:7149

Default Gateway . . . . . . . . . : 2002:c058:6301::c058:6301

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : D8-44-71-49

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:216.68.113.73%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled

Tunnel adapter Automatic Tunneling Pseudo-Interface:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : Automatic Tunneling Pseudo-Interface

Physical Address. . . . . . . . . : C0-A8-00-01

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : fe80::5efe:192.168.0.1%2

Default Gateway . . . . . . . . . :

DNS Servers . . . . . . . . . . . : fec0:0:0:ffff::1%1

fec0:0:0:ffff::2%1

fec0:0:0:ffff::3%1

NetBIOS over Tcpip. . . . . . . . : Disabled

===== From the laptop computer, docked:

Windows IP Configuration

Host Name . . . . . . . . . . . . : tardis

Primary Dns Suffix . . . . . . . :

Node Type . . . . . . . . . . . . : Unknown

IP Routing Enabled. . . . . . . . : No

WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter WORKGROUP:

Connection-specific DNS Suffix . :

Description . . . . . . . . . . . : 3Com 3C920 Integrated Fast Ethernet Controller (3C905C-TX Compatible)

Physical Address. . . . . . . . . : 00-08-74-42-1F-BC

Dhcp Enabled. . . . . . . . . . . : No

IP Address. . . . . . . . . . . . : 192.168.0.3

Subnet Mask . . . . . . . . . . . : 255.255.255.0

Default Gateway . . . . . . . . . :

by rob miners

on tardis change the gateway to 192.168.0.1 and on both PC's try this.

Click Start, Run and type cmd and press Enter.

at the command prompt type netsh winsock reset and then press ENTER.

Click Start, click Control Panel

Click Network Connections.

Right-click "Local Area Connection", and then click "Properties".

Click on (highlight) "Internet Protocol (TCP/IP)", and then click "Properties" button

Click the General tab, and then click "Advanced" button , bottom right.

Click the WINS tab.

Under "NetBIOS setting" section, click Enable NetBIOS over TCP/IP, and then click OK two times, then "close".

( ) Default

(*) Enable NetBios

( ) Disable NetBios

Keep us informed as to your progress if you require further assistance.

If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. ;) :D

by jim.poltrone

I did this, and rebooted both systems. I'm still able to ping. But I'm still not seeing any network places or workgroup machines on orac, not even itself. Hmmm..... What's next?

Before bringing my question here, I tried "regsvr32 wkssvc.dll", and got "wkssvc.dll loaded, but the DLLRegisterServer entry point was not found. This file cannot be registered." Don't know if this an XP Pro only thing, though.

Thanks for sticking with me on this.

by rob miners

running sfc /scannow by typing it in the run box. Double check that the Client for Microsoft Networks service is installed.

by rob miners

You could try and replace the dll from the XP CD. Unregister it first then expand the new file and reregister it.

regsvr32 /u c:\windows\system32\wkssvc.dll

Expand d:\i386\wkssvc.dl_ c:\windows\system32\wkssvc.dll

regsvr32 c:\windows\system32\wkssvc.dll

Keep us informed as to your progress if you require further assistance.

If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. ;) :D

by jim.poltrone

Ran sfc /scannow. It didn't ask to retry files this time, for which I'm thankful. (I previously tried sfc /scannow and it kept asking me to retry files.) I then rebooted. I then looked at My Network Places. Still nothing.

I then tried to unregister and reregister wkssvc.dll. I got the same errors: "wkssvc.dll was loaded, but the DllUnregisterServer entry point was not found. This file cannot be registered." and
"wkssvc.dll was loaded, but the DllRegisterServer entry point was not found. This file cannot be registered."

I think we've found the root of the problem.

by rob miners

Click Start, Run and type services.msc and press Enter.

Check to see if the Workstation Service is running. It should be set to Automatic. If it is not running start it. If it is running stop it and restart it. See if you get any errors.

< Edit to add >
You didn't say whether or not the Client service is installed. You also said that you have reinstalled windows. Was that a repair/install or a full install. You have loaded all of the motherboard and drivers for the NIC.

Keep us informed as to your progress if you require further assistance.

If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. ;) :D

by rob miners

is compatable with SP3. I am going to leave the ball in your court. With what we have already tried you should have a connection. You can try a registry cleaner like ccleaner which I doubt will achieve anything. I think that you have a corrupt registry. If it were me I would do the reinstall and start fresh. That way you only have to reinstall what you currently need to use. You should have a Backup plan for when situations like this occur. The only other suggestion that I can think of is malware. It wouldn't hurt to try this.

Download Malwarebytes Anti-Malware.

http://download.bleepingcomputer.com/malwarebytes/mbam-setup.exe

* Double-click mbam-setup.exe and follow the prompts to install the program.
* At the end, be sure a checkmark is placed next to Update Malwarebytes' Anti-Malware and Launch Malwarebytes' Anti-Malware, then click Finish.
* If an update is found, it will download and install the latest version.
* Once the program has loaded, select Perform Quick Scan, then click Scan.
* When the scan is complete, click OK, then Show Results to view the results.
* Be sure that everything is checked, and click Remove Selected.

I would keep scanning with it until it is clean by closing out and rebooting and running it again.

Just to be on the safe side when you finish do an online scan with Bitdefender.

http://www.bitdefender.com/scan8/ie.html

I will have another look at you ipconfig files.

Keep us informed as to your progress if you require further assistance.

If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. ;) :D

by jim.poltrone

I wish Microsoft's diagnostic tool was compatible under SP3. Instead, I get the message "Setup has detected that the Service Pack version of this system is newer than the update you are applying. There is no need to install this update."

In the meantime, I had an idea. I have a working network, even if the application layer of Windows thinks I don't. Why not run an ftp server on the laptop and an ftp client on the desktop and use them to transfer files? I have a rudimentary version working on both systems. I'm in the process of switching over to the FileZilla client and server. It's not an ideal system, but it will get the job done.

I also have a testbed system on which I performed a brand new install of XP. I created a couple of shared directories, called Incoming and Outgoing. They're not automatically visible in My Network Places. When I view my workgroup computers on the testbed, I get the workgroup name with no computers, not just a ding (which is what kept happening on the desktop).

by jim.poltrone

Workstation Services was running; was stopped and restarted. No errors.

Can't find a service called "Client", but I found DHCP Client, DNS Client and WebClient.

As for the reinstall, I'm not sure. I didn't use the Recovery Console; I just used the menu from the XP CD. I'll assume it was a full reinstall.

by rob miners

Go to Control Panel, Network and Internet Connections, Network Connections, right click on Local Area Connection, click Properties. Now look at what you have in front of you.

On the General Tab you should have Connect using. And there will be a description of your Network Card. And under that you should see. This connection uses the following items: Below that you should see Client for Microsoft Networks with a box to the left of it with a Tick in it.

If Client for Microsoft Networks is not there or it hasn't got a Tick in it put a Tick in it or you will have to add it by clicking Install, select Client and click Add. Select it from the list and click OK.

by jim.poltrone

Client for Microsoft Networks, File and Printer Sharing for Microsoft Networks, and Internet Protocol (TCP/IP) all appear and are checked.

And still nothing appears in My Network Places.

Ready to give up yet? :)

by rob miners

Did you replace the wkssvc.dll file from the XP CD and try to register it.

On your orac PC create a Share and give everyone permisssion to access it.

Step 1: Click the Start button and select Run. Now type the following text in the Run box and press Enter:

notepad c:\WINDOWS\system32\drivers\etc\hosts

Step 2: You will see a new notepad window on your screen containing some information. You should have a single entry of 127.0.0.1 localhost.

Add an entry 192.168.0.1 orac save the file and restart the PC.

Now go to a command prompt and type net use J: \\orac\sharename

Let us know what the error message is. Also look at your Event Logs with event viewer to see if there are any errors.

by jim.poltrone

wkssvc.dll was replaced and am still unable to register it.

I also added a new share called Outgoing, added the entry for orac in hosts, and rebooted. When I tried to map the drive in the command prompt, I got "System error 53 has occurred. The network path was not found." I had a similar error when I tried to map it from My Computer|Tools|Map Network Drive: "The network path \\orac\Outgoing was not found."

The only thing i could find in the security log was this:
Logon Failure:
Reason: Unknown user name or bad password
User Name: jim
Domain: ORAC
Logon Type: 2
Logon Process: Advapi
Authentication Package: Negotiate
Workstation Name: ORAC

For more information, see Help and Support Center at http://go.microsoft.com/fwlink/events.asp.

You're right; something's really messed up here. :( I guess it's to be expected for an 8-year-old machine that was upgraded from Win 98 SE. I'm considering running a registry scrubber to get rid of the cruft that's accumulated over the years.

by rob miners

and I think that it is beyond a registry clean. Get your XP Motherboard and extra drivers ready. EG: NIC and Video. Then try setting up your network connection.

Perform a clean install of Windows XP and delete the Primary Partition and recreate the Primary Partition on the fly. By doing it this way you will have XP from the onset and you will need to have your Win98 CD handy because you will be asked for it during the install. Just insert the Win98 when you are asked for it and follow the instructions. Backup your Data before proceeding.

1. Start your computer from the Windows XP CD. To do this, insert the Windows XP CD into your CD drive or DVD drive, and then restart your computer.

2. When you see the "Press any key to boot from CD" message, press any key to start the computer from the Windows XP CD.

3. At the Welcome to Setup screen, press ENTER to start Windows XP Setup.

4. Read the Microsoft Software License Terms, and then press F8.

5. Follow the instructions on the screen to select and format a partition where you want to install Windows XP. At this stage you can select to delete the Primary Partition and recreate it. Then continue with the install.

6. Follow the instructions on the screen to complete Windows XP Setup.

http://support.microsoft.com/kb/316941/en-us

Keep us informed as to your progress if you require further assistance.

If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. ;) :D

by jim.poltrone

I was hoping to avoid a full reinstall. I have so many pieces of software on my system that it would take me days, if not weeks, to reinstall everything.

I did find an XP network diagnostic tool (MS Knowledge Base #914440), but alas, it only works under SP2. I already installed SP3 and it won't work for me. I may have to rollback SP3, run the tool, and then reinstall SP3.

Thank you for your time and effort in trying to help me fix this problem. I really do appreciate it.

by cg it

your using a cross over cable between the 2 machines, so are they connected to the internet as well?

by jim.poltrone

I'm only connected to the Internet when I dial in. (My preferred DSL provider doesn't service my area, and my cable TV company gets enough of my money already.) It's not a shared connection.

I had a 4-connection hub, but put it in storage when I tried to upgrade to a wireless router (see previous posts for more details). Even if I went back to the hub, I think I'd still have the same problem because the desktop machine can't even see itself in the list of workgroup computers.

by rob miners

Double check your Logon ID and password. Also try this if removing TCP IPv6 doesn't work.

http://www.iup.edu/house/resnet/WinsockXPFix.exe

Keep us informed as to your progress if you require further assistance.

If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. ;) :D

by cg it

since you mentioned that you have read the Microsoft 8 part series in setting up a small network, then you should be familiar with the procedure of creating a workgroup [not using the existing workgroup] joining all the computers to the same workgroup, then sharing files and folders. Further, you have to install file and print sharing protocol and have it enabled [find this in the network properties of the Network card.

note: all computers must be on the same subnet meaning that if you use the private address 192.168.1.1 through 254 , mask 255.255.255.0 then all computer's addresses must be using that same range and subnet mask. Again, this is in the 8 part series. Crossover cable [direct connection] requires some configuration to work.

here's a Microsoft technet article part 1 of 8 parts on how to get it to work.

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

if you follow these instructions you should be able to share files and folders between 2 machines via a direct connection.

by rob miners

I took it that this statement "I can ping each of the machines, regardless of which machine I'm on" meant that he was pinging the other PC. Was he pinging the loopback address? I did provide information on using ping. That is the basis that I made my assumptions on.

Rob

by cg it

Somewhere I read he was trying to ping himself and was unsuccessful and the method he was using was not using the 127.0.0.1 loopback address.

Then he was trying to connect to himself using the \\ which will never work because there is no network path to the same computer.

He should not have to buy XP pro to get networking between 2 computers going. He also shouldn't have to reinstall the operating system to get networking between 2 computers going unless there was a problem with the operating system before he attempted networking.

Windows XP Home will network with XP Pro just fine.

If he can ping, then he has connectivity between machines. He should be able to connect to another machine on the same subnet using the administrative share \\\C$ even if the computer don't belong to the same workgroup.

Unless a computer is sharing a folder, shares will not show up under my network places in their respective workgroups. Computers in different workgroups usually show up under my network places as multiple workgroups.

There is a known problem with using the network setup wizard in Windows XP Home. Here's a MS KB on it.

http://support.microsoft.com/kb/823305/en-us

I don't use the network setup wizard rather use the manual way. It could be that when he ran the network setup wizard, that caused the problems.

by jim.poltrone

(I'm posting my reply to the ping here since I hit the depth limit on the previous thread.)

As I said before, I'm able to ping my desktop and my laptop from my desktop. And I'm able to ping my desktop and laptop from my laptop. That was covered previously.

by rob miners

from the information in the post below this one.

Logon to tardis and try connecting to orac by its IP address, i.e., start, run, and type \\192.168.0.1\c$ click OK.

Let us know what the error message is if you get one.

by rob miners

Those OS's are probably the most stable. I like XP Pro with the new service pack. As I mentioned to someone the other day that I can trust XP Pro but I haven't came to the same conclusion with Vista yet. Vista Business and Ultimate seem to be the most stable at the moment but I sit at it waiting for something to go wrong. Maybe it's because of the Beta days when there was one thing after another going wrong.

by rob miners

for a small outlay you can connect a couple of PC's to the ports on a hub. I consider using a crossover the next step up from null modem. Very limited.

by jim.poltrone

I tried everything Jacky suggested (with the exception of wiping clean and reinstalling XP).

Client for Microsoft Windows is installed and checked. File and printer sharing for Microsoft Windows is installed and checked. TCP/IP is installed, checked, and configured. But still, when I try to view my workgroup computers, all I get is a ding. And if I try to create a new network place, Microsoft Windows Network still doesn't show up under Entire Network.

I fail to see how/why switching from my crossover cable to a hub will solve my problem.

by cg it

are proven methods of setting up a small network and connecting 2 computers together via cross over cable. I've setup many a network for small businesses that don't need a domain the same way the small network article mentions [not using the network connection disk metnod that you take around to other computers]. I've also used the cross over cable method but only for test bed stuff, but I know that works.

The only thing I can suggest is start over again from the beginning [first join each computer to a workgroup named workgroup, reboot then start setting up your network].

As far as using a hub, instead of a direct connection,

here is what the 8 part series, part 1 says about direct connections.

Part 1. Introduction: Configure a Direct Cable Connection with Windows XP Home Edition
For the occasional exchange of data between a laptop computer and a desktop computer, you do not have to use a whole network. If you use only a direct cable connection and a cable, you create a real network connection that you can quickly create and disconnect.

The direct cable connection is a connection between a guest computer and a host computer. When you use this connection, you can connect two computers to each other.? The host computer provides resources such as folders, drives, or even a printer.
? The guest computer uses the resources that the host computer provides.
Strict task sharing results in a one-way direct cable connection. The resources can only be accessed in one direction. To change the direction, disconnect an existing connection, reassign the tasks, and then reestablish the connection.

The last part here is the reason using a switch [not hub] is prefered. A switch provides 2 way connections between hosts. A direction connection is one way. The guest computer accesses the host computer and only the guest computer can access resources. The host computer can not access resources on the guest computer.

If you want the host computer to access stuff on the guest computer, you have to change the guest to host and reestablish the connection. It's some work and a pain to do where if you have a $25.00 USD 4 port switch, setting up simple file/folder sharing is easy to do.

If you still want to use a cross over cable and having problems, it's possible that you have to guest and host changed up or check to make sure your physical connections and equipment are correct.

by jim.poltrone

I replaced the crossover cable with the hub and "spokes" (straight network cables), which slows my throughput speed to 10 Mbps. (I'm not spending more money for a network switch.) I then reviewed the instructions in the 8-part series and followed the instructions. The only part that was new to me was covered in part 5 (Set Up An Incoming Connection). I removed and reinstalled Client for Microsoft Networks and File and Printer Sharing.

Despite all this, I am still having the following problems, which is what I had when I posted the first article in the thread:
1) When I try to view my workgroup computers on my desktop computer, I get the "ding" sound and nothing more.
2) When I try to add a network place via browsing, and click on "Entire Network", I don't see "Microsoft Windows Network" listed, just "Microsoft Terminal Services" and "Web Client Network". (I expect to see Microsoft Windows Network listed; it shows up on XP Pro.)
3) If I run "\\orac" (the name of my desktop computer) from my desktop computer, I'm told "the network path was not found". (The machine can't find itself, even though it can ping itself.)
4) When I try to run "\\orac" from the laptop, I'm told the machine is not accessible, and that access is denied.

I really appreciate all the help, but I think Jacky's right. The only way I can truly fix this problem is to wipe clean and start over with a fresh reinstall.

by rob miners

can be a pain sometimes even when your PC's are running properly. By trying to connect again through your Hub should tell you wether or not you are going to be able to do it without a reinstall of the OS. The command to reload "regsvr32 wkssvc.dll" didn't work on my working system either, so we were barking up the wrong tree there.

by rob miners

How to troubleshoot missing network connections icons in Windows Server 2003 and in Windows XP

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

Keep us informed as to your progress if you require further assistance.

If you think that any of the posts that have been made by all TR Members, have solved or contributed to solving the problem, please Mark them as Helpful so that others may benefit from the outcome. ;) :D

by cg it

if you can not ping other machines on the network, then you have connectivity problem. Connectivity problems can mean that the computer your trying to ping is not on the same subnet, a network card is bad, a network cable is bad, you have a corrupt TCP/IP stack, etc.

Not being able to see computers that belong to the same workgroup usually means that they either have connectivity problems [either their not on the same subnet [address and subnet mask are wrong], a firewall is blocking or they have lost their workgroup membership.

If you don't see any shares listed in my network places at all, did you share something? have to share a file or folder for it to be seen. If you have not shared anything on the computer, try \\\C$ [not your computer but the other one ] which is the administrative share for the C: drive. [note the $ sign means that the share is a hidden share] If both are on the same subnet,have connectivity with each other [ping], you should be prompted for credentials to log on.

If your trying to ping one's self, [your own computer] you use the the loopback address 127.0.0.1 you should always get a reply from yourself. If you don't, you may have a faulty network card which might be the cause for connectivity problems with other computers.

Note: loopback address is an address that sends outgoing signals back to the same computer for testing. In a TCP/IP network, the loopback IP address is 127.0.0.1, and pinging it will always return a reply.

before you try to connect to yourself using the \\ think about how data packets must travel. They must go out the network adapter and then come back in to the same network adapter. If there is not way for a packet to travel out and then back in, you will always get "network path not found" as there is no network path to yourself [\\yourself , rather the "path" on the computer your using for any file or folder on your computer is C:\\\

Note: I'm not an advocate of a clean install to solve problems unless it's a registry problem that can not be fixed.

by jim.poltrone

When I try that command from tardis I get "The network path was not found" after about a minute of waiting. Which is curious, because I tried pinging orac from tardis before executing the \\192.168.0.1\c$ command and got an immediate response from the ping.

As for registry settings, which ones should I check? I'm a little reluctant to start mucking around in the registry, especially since I've received so many Dire Warnings if I make a mistake.

by rob miners

it may be the answer to your problems. ;)

If not I will prepare a step by step guide for you to navigate around the registry. I have a few things for you to check. :D

by cg it

you should have been able to connect to the administrative share C$, given that both computers are on the same subnet and both belong to the same workgroup

[you created a workgroup by joining both computers to the same workgroup [eg you made up a workgroup name like Office or Home, joinged each computer to that workgroup by going to control panel\system and clicking the computer name tab, on the computer name property page, you clicked the change radio button to rename the computer or join a domain. clicking that radio button opens the computer name change property sheet. In the box for workgroup, you changed the workgroup named "workgroup" to whatever name you picked, clicked ok and received the reboot necessary for changes to take effect message, you rebooted [both computers] then logged on. ]

Note: whenever you try to "redo" a workgroup if the first one doesn't work, you have to change the workgroup name to something different, reboot, then change it back again, then reboot.

I know the MS KB articles for setting up a small network work. I don't use the network wizard that creates a disk you take to another machine. Never had much luck with it. I prefer to create a workgroup name, join each computer to the workgroup using the control panel\system\computer name\change name-join domian method. It's a fool proof method.

Usually when a computer's shared folder in a workgroup is inaccessible, the computer hosting the share either lost connectivity, or lost it's workgroup affiliation.

If you have tried the proven methods of creating a workgroup, verified that you have connectivity between computers, verified that a firewall isn't blocking traffic between the computers, and still can not access shared resources between computers that belong to the sames workgroup, I'm hesitant to say you might have a more serious underlying problem with one or both computers but maybe that's the problem. ::::shrug::::

by rob miners

is a pain in the butt. It doesn't have default Admin Shares and a lot of other things that XP Pro has. I keep forgetting about its misgivings and treat it like XP Pro but you can't. There are the same problems coming up with Vista Basic. If the bean counters at Microsoft would let the developers concentrate on one universal OS that would work properly out of the box we would all be laughing. All of these different Versions are a joke.

by rob miners

explain it. I never use the wizard either so I am unfamiliar with its shortcomings. That was a good pickup and lets hope that it solves the problem.

I sat in the shed for a couple of hours connecting to my Acer Notebook which has XP Home on it. I was using Vista as it has a couple of extra diagnostic wizards that can be run if it encounters a problem. I deliberately tried to connect to a non existent share to see what would happen.

Error code: 0x80070035

The network path was not found

This was the response after running the wizard. Windows confirmed that the server "10.20.20.26" exists but cannot find C$

This is along the lines of the error that Jim received about the network path. So I do think that he is connecting but something is stopping the connection. Lets hope for Jim's sake that you have nailed it.

by jim.poltrone

Checked the MS KB article and checked to see if I had such a network bridge. I didn't.

Just curious, CG: have you been keeping up with all the posts on this thread? I know there's a lot here; maybe we have the record for most posts in a thread. Perhaps there's a detail that we've overlooked.

by cg it

I usually will read posts from TR members I know. I also try to read all of the authors posts in reply to any suggestion.

I do however get questions mixed up sometimes. I remember reviewing a question and one of my answers and I wondered why the heck did I say that only to find that it applied to another question. And in that question was the suggest for the other one.

by rob miners

make sure the Telephony, Remote Access Connection Manager, and Remote Access Auto Connection Manager services are running.

Verify that the Objectname string value is set to LocalSystem in the following registry subkey:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan

Note This procedure includes steps to back up the registry keys before you modify them.
Click Start, and then click Run.
In the Open box, type regedit, and then click OK.
Locate and then click the following key in the registry:
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\RasMan
On the File menu, click Export.
In the File Name box, type exported rasman key, and then click Save.
In the RasMan key, locate and then click the ObjectName string value.

If this value is not set to LocalSystem, follow these steps:
a. On the Edit menu, click Modify.
b. In the Value data box, type LocalSystem, and then click OK.

Quit registry editor, and then restart your computer.

by jim.poltrone

Services are running, although Remote Access Connection Manager and Remote Access Auto connection are started up manually. (I still use dial-up to connect to my internet service provider.)

I also checked the RasMan settings in the registry, and ObjectName was already set to LocalSystem.

Despite this fix, I still can't create a network place or view other machines in my workgroup. I wonder if there's some other service that needs to be added and running.

by rob miners

To resolve this issue, use Registry Editor (Regedit.exe) to locate the following key in the registry:
HKEY_LOCAL_MACHINE\System\CurrentControlSet\Services\Netbt\Parameters\
Change the value of the EnableProxy value in the preceding registry key to 0 or 1, quit Registry Editor, and then restart your computer.

< Edit >
You will have to do this on both PC's.

by cg it

Windows 2000 Professional, Windows XP Professional, and Windows Vista Business are usually what I deal with. Some small offices have a mix of XP Pro and Home, but never had a problem creating workgroups, sharing folders and printers. Have had intermittent connection problems and that's from the wireless clients who drop their wireless connection for no reason but wired, they are pretty reliable.

I dunno, I find that problems with computers and workgroups [AD domains as well] isn't some "not seen before" problem.

Watch, he'll come back, tell us he reinstalled XP and volia! network works.

by jim.poltrone

Saw that the value of this setting was 2. Changed it to 0, rebooted, and did my usual tests (ping, add new network place, view workgroup computers). No difference. Went back to the registry and saw that the value of this setting was changed back to 2. (No, I did not change the setting on the other computer. Is that what's causing this value to revert?) Changed it to 1 and repeated what I did before. The same result. Although now when I try to repair my connection, I can't clear the ARP cache.

by rob miners

After the installation of Service Pack 2 or 3, this service is set from Manual to Disabled by default on Windows XP Pro.

To disable Routing and Remote Services:

Click the button
Click the button
Switch to "Classic View" if you are in "Category View"
Click
Click
Double-click
Double-click
Scroll down to
Double-click
Examine the "Startup Type"
The options are "Automatic", "Manual", and "Disabled"
Set the "Startup Type" to "Disabled"
Examine the "Service status"
Make sure that the service status is Stopped. If it is not Stopped, click the button
Click the button
Now, try clearing the ARP cache again and it should complete with no error messages

From the desktop computer (while logged in to my ISP):

Have you tried any of these fixes without being logged into your ISP.

by dondon1205

I have an experienced like this. Have a connection but only limited to 10mbps..I just reinstall the windows and it works smoothly..

by jim.poltrone

Thanks to this, I was able to clear the ARP cache. But the original problem still remains.

Can't remember if these fixes were attempted while standalone. I would think it wouldn't matter, since I dial in to my ISP instead of using broadband (DSL or cable). That's something to consider if/when I finally get employed again.

by rob miners

The Computer Browser service is running and it is set to Automatic.

by rob miners

too well what it is like to be unemployed. Welcome to the club. :D

by rob miners

Do you have any Firewalls running.

What Antivirus are you using.

You could temporarily disable the Firewall, check connection re-enable if not the problem and do the same with the Antivirus. You should be able to disable the Antivirus through msconfig.

When you plug in the Crossover Cable do you see this, Local Area Connection is now connected.

Logon to Tardis and check to see if it is being registerd by checking the output from NBTStat, which is a standard Windows "NetBIOS over TCPIP" utility.

C:\>nbtstat -A 192.168.0.1

Example: NetBIOS Remote Machine Name Table

Name Type Status
---------------------------------------------
orac <00> UNIQUE Registered
workgroup <00> GROUP Registered
workgroup <1E> GROUP Registered
orac <20> UNIQUE Registered

MAC Address =

by rob miners

Check this Registry setting as it should look like this

[HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Control\Lsa] "restrictanonymous"=dword:00000000

If it has a dword value like dword:00000001 right mouse click on it and select Modify and change the 1 to a 0

let me know how you get on.

Rob

< Forgot to add where the info came from >

https://www.techrepublic.com.com/5208-1035-0.html?forumID=101&threadID=205033&messageID=2129517

I don't know if the poster that was mucking around was bored but it may help.

by skipperthedog

cant map drives, cant connect to other machines on the network. "Microsoft Windows Network" icon is missing, when I click on view network computers I get a MS error beep.
Read all the replies and Im rolling back to SP2 and trying the Diag tool. very troublesome indeed.

by rob miners

but if you try all of the responses here you may get it to work. Mark them off as you go so that you don't get confused. Let us know how you get on.

by skipperthedog

I did indeed try all of the fixes, and a number of my own. I can rdp, ping and resolve to any PC on my network, but I cant connect via explorer or drive mapping (//10.0.0.111 for example)All of the other PCs can connect to any other PC and see the shares. Its XP Pro, Home, win2003, and a win2008 box. I know the shares are there. I have no AV installed, and Windows firewall is set to off. Ive literally spent weeks trying to resolve this. I hate to give this machine up as I have yrs of programs, settings and custimzation I dont want to have to rebuild.
The icon is missing, cant map drives (even to myself) clicking on view workgroup computers gives me a windows error beep. I also strangely enough have two residual "network shares" that are stuck in my network places, they are both valid and can be explored. they are: [10.0.0.187share on 10.0.0.187] and [local on 10.0.0.187] which are to a win2003 box. At one point before this all failed I had drives mapped to these shares from this machine. I can click on these "places" and browse, but I cant see the other shares on this PC (or printers)

by rob miners

If you have tried all of these suggestions and it is still not working you have a few problems. Have you tried a System Restore. If that doesn't work I think that you will have no other choice other than to rebuild.

You could back up the existing registry files to a new location, delete the registry files at their existing location, and then copy the registry files from the repair folder to the System32\Config folder. When you have finished this procedure, a registry is created that you can use to start Windows XP. This registry was created and saved during the initial setup of Windows XP. Therefore any changes and settings that occurred after the Setup program was finished are lost. Doing this you would be back to square one with no Programs installed.

I can't see any other way out of it unless another peer has any suggestions.

This discussion is closed to new replies.