Two pc's can only "see" each other if I boot up the XP machine first and then the 95 machine but not the other way around

Hello, I have connect two computers together using the software buit into microsoft windows. One pc is running XP and the other 95.

The problem that I am having is that the two pc's can only "see" each other if I boot up the XP machine first and then the 95 machine but not the other way around.

If I do boot up the XP machine fist, it can "see" the files on the 95 pc but the 95 pc can't "see" the files on the XP machine.

Thanks, Jon

Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Have you enabled netbios on XP?

 check your XP networking setup:
Although this link says to set netbios over tcp/ip to "default", follow the instructions below...
Turn on "Simple file sharing" on the XP (Pro only) machine. Open explorer, click tools, click folder options, click the view tab and scroll down until you see "Use simple file sharing" then check the box..
For the duration of testing, enable the Guest account on XP. If all works, you can deal with that issue later (username/passwords for everyone on every PC)
Client for Microsoft Networks needs to be the primary network logon for all other machines
All machines are in the same workgroup

Enable NetBios over TCP/IP in WIndows XP
Step 1: Turn On NetBIOS over TCP/IP
Click Start, click Control Panel, and then click Network and Internet Connections.
Click Network Connections.
Right-click Local Area Connection, and then click Properties.
Click Internet Protocol (TCP/IP), and then click Properties.
Click the General tab, and then click Advanced.
Click the WINS tab.
Under NetBIOS setting, click Enable NetBIOS over TCP/IP, and then click OK two times.
Click Close to close the Local Area Connection Properties dialog box.
Close the Network Connections window.

Step 2: Start the Computer Browser Service
Click Start, right-click My Computer, and then click Manage.
In the console tree, expand Services and Applications.
Click Services.
In the right details pane, verify that the Computer Browser service is started, right-click Computer Browser, and then click Start.
Close the Computer Management window.


Install NETBEUI only if you have no other choice:
Make sure the XP firewall is off.  If you still want a firewall, ZoneAlarm is a nice, easily configured one.
acsellAuthor Commented:
Thank you for your help. I have been through the instructions that you have given above and the website links. I have also got the firewalls disabled. I am still having thye same problem.

The only thing I didn't understand is about the passwords. I am using windows XP home edition. On the windows 95 machine I have a password come up to log on to the network but I just put my name as the username and left the rest blank.

I also wasn't sure which items to leave  in network settings. One of the websites said to delete the ones you didn't need.

Also there seemed to be some contradictions on the websites above. Some say to set the IP address and mask and others say to set it to automatic. I am also not sure how to set the dns settings (or whether I need to) when I set the IP address. I'm sharing the internet over a proxy server.

At the moment I have the IP set up as follows-

XP- subnet mask-
95- subnet mask-

Thank you very much for your help so far,

SolarWinds® VoIP and Network Quality Manager(VNQM)

WAN and VoIP monitoring tools that can help with troubleshooting via an intuitive web interface. Review quality of service data, including jitter, latency, packet loss, and MOS. Troubleshoot call performance and correlate call issues with WAN performance for Cisco and Avaya calls

Try enabling the Guest account on the XP box?
acsellAuthor Commented:
Hello, I have enabled the guest account, but that is all I have done on the guest account.
acsellAuthor Commented:
I've noticed you've said Install NETBEUI only if you have no other choice, what would be the disadvantage of using NETBEUI  and might that solve the problem.

Thanks, Jon
There's no real disadvantage, and it could solve your problems.
Look in the Xp box's Event Viewer and look for any error messages that might lead to looking at other things..

Even if you can't "see" one another in Network neighborhood, can you still ping each other?
Try pinging both by IP address and then by name:
From XP:

C:\>ping [95] <-- use name of PC

From 95:
C:\>ping [XP]

which ones work, which ones fail?
acsellAuthor Commented:

I have managed to ping from both pc's successfully, even when they couldn't "see" each other. Although first time I tried, the firewall blocked the pings.

I have looked in events viewer and there were quite a few errors from today. Here are the main two-

The browser has received an illegal datagram from the remote computer EVESHAM to name MSHOME on transport NetBT_Tcpip_{901B545E-D620.  The data is the datagram.
(mshome it the workgroup name)

While transmitting or receiving data, the server encountered a network error. Occassional errors are expected, but large amounts of these indicate a possible error in your network configuration.  The error status code is contained within the returned data (formatted as Words) and may point you towards the problem.

0000: 00040000 00540001 00000000 800007dc
0010: 00000000 c001001f 00000000 00000000
0020: 00000000 00000000 0000099d
(I have had quite a few of these)

To add to my original post, I seem to be able to view the files from the 95 pc on the XP pc all of the time the 95 pc is on. I can only see the files on the 95 machine after restarting the xp machine, although I can still use the internet on it using the proxy server.

Thanks for your help, Jon

How do you have these two physically connected to each other? I'm beginning to suspect physical layer issues like a duplex condition... Are you using a crossover cable, or a hub/switch?

Apparently, the TCP/IP communications are working just fine, just not the Netbios.
You mentioned turning off the firewall....
Have you tried using a LMHOSTS file on the Xp box with the ip address of the 95 machine?


create text file with only one entry: <tab>  EVESHAM

Save the file as "lmhosts" with no .txt or any other file extension

Then use the nbtstat command:
C:\>nbtstat -RR

Try ping by name
c:\>ping evesham

If you get response, then we're closer than before.

Looks like I didn't finish my thought process here:

You mentioned turning off the firewall....

which firewall? Xp's built in? Other? Is it on the XP box or 95 box?
If you are going through a 3d machine as a proxy, you don't really  need it on that box either..
acsellAuthor Commented:
Hello, Thank you for your quick response.

I have connectected the two pc's with one NIC in both pc's and one cable, not sure what kind though.

I haven't got a firewall on the 95 pc. On the XP pc I have always had the built in one turned off and I use kerio personal firewall.

I created the lmhosts file like you said but with <tab>  Richard
Richard is the name I've given to the 95 pc.

I used the C:\>nbtstat -RR command from both pc's.

The xp one said-
"The NetBios names registered by this computer have been refreshed"

The 95 one said-
"Successful Purge and preload of NBT Remote Cache name Table"

I also pinged each pc again useing the name of each pc. They both recieved all packets.

Thanks for your continued help, I appreciate it.
Looks like progress...
Is there any change in the way things look from the perspective of the original post?

I would highly suggest getting yourself a little 4-port Ethernet switch to put inbetween your computers instead of a single crossover cable. The fact that you can ping back/forth means that the cable is probably correct, but you can have duplex issues where both PC's network cards are set for autonegotiation, and because they are not connected to a switch to negotiate with, one may default to half-duplex, and the other to full-duplex. This causes all kinds of errors that are not easy to spot or define. Basically, poor network performance. You can try manually setting both network cards to 100Mb/HALF-duplex. Depending on the make/model and driver, that setting should be easy to find in the adapter properties.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
acsellAuthor Commented:
Hello, thanks for your help,

I will look into the switch as long as it's not too expensive. It's quite an old machine I'm connecting to so I don't want to spend too much on it.

I had a look in the network settings but I can't see anything to do with duplex. I had a look at what speed the network place said it was running at and it said 100mb/s. I can't find anything about the speed of the transfer on the 95 pc.

I did try updating the drivers for the NIC but I must have installed the wrong ones because I had to do a system restore to get card to work again.

I am still having the same problem with the 95 pc not seeing the xp pc. It's a bit odd because the network seems to work fine as long as I start the 95 machine up first.

Thanks, Jon
acsellAuthor Commented:
Hi, Just incase anyone else had the same problem I thought I'd post about how I've gotten on. I decided to install Netbui on both machines and the network seems to running OK now. I still don't completely understand while it wasn't working on TCP/IP.

Thanks lrmoore for your help in solving this for me and congratulations on becoming the top networking expert of the year.

It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today

From novice to tech pro — start learning today.