Discussion Locked

Networking Errors

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

I have a network at home that uses XP Pro and Win 98 SE. I am having the following errors.
1. when I go to browse the network on the Win 98 SE machine I get the error "Unable to browse the network". I can ping the other machines in the network and the router. I have reloaded Win 98 in case if some were files got dumped.
2. This is more of hummmm, but when I run network trouble shooter, after the first screen the screen goes blank.
3. Once I get everything up and running to the point where I can access the network do I have to run the XP network disk on the Win 98 SE machine
Thanks

14 replies

by 3xp3rt

This problem comes from the two type of file system. Win98 use FAT32 file system, and XP use NTFS file system. The win98 can?t read NTFS file system. The solution is to install WinXp on FAT32 file system.

by hal 9000

What should be happening here is that you run the Network Setup Wizard on the XP machine and create a Floppy when you finish. Use this Floppy in the 98 machine to setup the network and it should work.

Col

by hal 9000

From your additional posts it appears as if the 98 machine/s are not setup correctly to work on the network. That is what you need the floppy that you created with XP for to install the correct drivers in a Peer to Peer Network so that the 98 machine/s can properly interact with the XP machine/s.

When you load from the floppy you should be asked to remove the floppy and reboot after the network file is installed and then on the reboot you get to setup the network settings and sharing.

Col

by master3bs

Additionally, I've found that 98 machines can have problems accessing network resources on XP machines (such as printers) if the 98 machine isn't setup to logon to the domain.

Go to the 98 network properties, and then into the Client for MS Networks properties. Set it up here to logon to the domain.

by mtmccarty

Thanks everyone for their comments but one point is being missed. Is that when I go to browse the network I get the ERROR "Unable to browse the network" meaning I can't even see myself in Network Neighborhood.
Mark

by otl

A. 98 machine set up for ICS ?

B. All on the same domain ?

C. ICS set up on XP boxes ? Win 98 login/machine loaded on them ?

D. Router/switch set up to allow checking other ports ?

E. Can not run XP disk/programs on 98 machine, it will kill it must us the 98 setup disks on it.

by skidoggeruk

Workgroup name on 98 identification tab under network properties match the domain name?

I imagine you have checked ip,mask&GW a million times

Good Luck

BK

by mtmccarty

Well it seems most of you have missed the point. The problem is with the Win 98 machine not with XP.
I repeat I cannot browse the network from the Win 98 machine this has nothing to do with the XP machine. I never said I was trying to access the XP machine. Just trying to access the network to see who was in the workgroup. The error is "UNABLE TO BROWSE THE NETWORK" the point is browse the network not access the XP machine

by blackcurrant

Hi

This can be caused by a couple of things.

First - are you using the correct driver for your network card? Our Win98 machines will not browse the network unless the correct driver is installed.

Second - are your DNS settings correct? Are you getting DHCP from the router or are you using static IP addresses? If the latter, then you need to make sure that both computers use the same initial information: e.g. 192.168.0.1 and 192.168.0.2. You also need to make sure that the subnet mask is the same on both machines (usually 255.255.255.0). You then specify the internal IP address of the router as the gateway (192.168.0.x), which enables access to the Internet.

As said above, you also need to make sure that your domain/workgroup is specified if you use the logon screen, and also make sure that Microsoft File and Printer sharing is enabled.

Good luck

by gary56789

Are you running a firewall on the 98 makchine? If so, you will need to add the IP address and name of the other computer on your network to the firewall configuration.

Also, after trying to access Entire Network from the 98 machine, enter the name of the XP machine in the Aearch for Computers area. If it is found, try to browse the XP computer to see if you can open whatever file(s) you have shared.

Concerning the Networking Troubleshooter, try the following MS link

http://support.microsoft.com/default.aspx?scid=kb;en-us;193938

Repost and let us know if this helps.

by rickrbyrne

Really all you should have to do is make sure that the computers are all in the same workgroup, For example if your workgroup name is "HOME" make sure that the windows xp computer and windows 98 computer are both in a workgroup called "HOME", now for the Windows 98 Computer make sure that you have File and Print Sharing Installed and Enabled and you should be fine, you should now be able to see your Windows 98 computer. If you would like more details on installing and enableing File and print sharing, Post and i will explain more.

Rick

by ghenry0006

I will bet you anything if you simply click and then log back in on the WIN98 machine, you will have the network you are looking for.... Make sure you are in the same Workgroup as the XP machines and other 98 machines - you will need to create machine accounts to match "Logins" from 98 machines.
gjh

by mtmccarty

Ok, I found the problem. In the TCP/IP setting, the binding was turned off for "client for network neighborhood. I turned it back on and rebooted and it works great. And to give those that were talking about the XP and ICS. I ran the ICS floppy and it did nothing. I went into MSconfig and disabled the ICS and I access the XP machine meaning that on a network it doesn't care about FAT or NTFS. There is something called that called the redirector and it takes the users request and converts it to 1's and 0's and that how information is moved about on a network. Thank you for your time
Mark

This discussion is closed to new replies.