Entire Network Error

Hi,
We are trying to set up a Home Network with a Windows XP Home Edition computer and a Windows 98SE computer.
We are using a cable modem and a broadband router.
After we set everything up, we can see the shared files on the WinXP computer from the Win98SE computer but we cannot see the shared files on the Win98SE computer from the WinXP computer.
We can connect to the Internet with both computers.
We have also tried shutting down Zone Alarm on both computers. (We are not using the WinXP firewall.
When we go to My Network Places and click on Entire Network, then Microsoft Windows Network, we get the following message:

"Entire Network
Unable to browse the network.
The network is not present or not started.
For more Information, click Help
OK Help "
We are referred to KB article 256235 which covers this subject but the article is written for Windows ME and does not help us.

Any suggestions would be appreciated.
Thanks

 

Can you post your IP info? (start, run, cmd, then enter and run "ipconfig /all" from the DOS prompt) Copy and paste that info here......

 

Hi James,
Thanks for the reply. Here's the info:

Microsoft Windows XP [Version 5.1.2600]
(C) Copyright 1985-2001 Microsoft Corp.

C:\>IPCONFIG /ALL

Windows IP Configuration

Host Name . . . . . . . . . . . . : ibm-dkvo660hygr
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No

Ethernet adapter Local Area Connection 2:

Connection-specific DNS Suffix . :
Description . . . . . . . . . . . : Intel(R) PRO/100 VE Desktop Connecti
on #2
Physical Address. . . . . . . . . : 00-02-55-97-B6-67
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 192.168.0.100
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 192.168.0.1
DHCP Server . . . . . . . . . . . : 192.168.0.1
DNS Servers . . . . . . . . . . . : 192.168.0.1
Lease Obtained. . . . . . . . . . : Saturday, July 10, 2004 11:38:05 AM
Lease Expires . . . . . . . . . . : Saturday, July 17, 2004 11:38:05 AM

C:\>

C:\>

 

.

 

.

 

IP info for the Win98 computer......

 

Hi James,
Here's the additional info for Win98SE:

Host Name: IBMAPTIVA
DNS Servers: 192.168.0.1
Node Type: Broadcast
NetBIOS Scope ID:
IP Routing Enabled: No
WINS Proxy Enabled: No
NetBios Resolution Uses DND: No

Ethernet Adapter:
Description: D-Link DFE-530TX+ PCI Adapter
Physical Address: 00-40-05-36-F3-C6
DHCP Enabled: Yes
IP Address: 192.168.0.101
Subnet Mask: 255.255.255.0
Default Gateway: 192.168.0.1
DHCP Server: 192.168.0.1
Primary WINS Server:
Secondary WINS Server:
Lease Obtained: 07 11 04 10:32:00 AM
Lease Expires: 07-18-04 10:32:00 AM

For some unknown reason I couldn't paste this info from Word 2000 into the BBS forum.

Thanks.

 

Under your Local Area Connection, Properties, Internet Protocol TCP/IP.....try unchecking "Obtain an IP Address automatically" and manually entering your IP addresses. See what that does for you. Also, double check that both computers are members of the same workgroup.

 

Hi James,
Both computers are in the same workgroup.

We tried setting the IP Addresses manually but that didn't solve the problem.

 

Have you installed the File and Print sharing service on the Windows 98 computer? Without it, the 98 pc won't advertise its presence on the network. The option is available from the Network Properties. If memory serves me right, you add it in the same way as you add a protocol or Microsoft Networking.

 

Hi Reggie,

Yes, our File & Print Sharing is enabled on both computers.

Thanks

 

http://www.dlink.com.au/tech/faq/dfe530tx+_faq/#ad_3


3. Which protocols do I need to install? (Back to top)

If you are running a small Windows–based, peer-to-peer network and you do not intend to share Internet access among the computers on the network, then you only need a single, name–based protocol such as Microsoft’s NetBEUI. This protocol works by broadcasting the names of the computers (or devices) across the network each time you initiate a request for access to the resources of another computer or device (e.g., printer) in your workgroup. If you have a device such as a print server that requires the IPX/SPX protocol, you will need to install that protocol as well.
If you intend to share Internet access among the computers on your network, you will need to add the TCP/IP protocol to each PC. Subsequently, you must configure the TCP/IP Properties on each PC for either a manually–assigned or automatically–assigned IP address. If you are running a Client/Server network, at the very least, you will need to install the TCP/IP protocol. Your network may also require IPX/SPX as well. If you are in doubt as to which protocols you need, install all of them. This is sometimes referred to as being, fully–networked. On a small network you will see little, if any, performance degradation as the result of installing all of these protocol. On large networks, however, you may degrade performance by installing unnecessary protocols.

 

Hi LDTate,

This is what I have Installed on Windows XP Home Edition

Connect using: Intel(R) PRO/100 VE Desktop Connection #2
Client for Microsoft Network
Service Advertising Protocol
File & Printing Sharing for Microsoft Networks
QoS Packet Scheduler (Not Checked)
NetBEUI Protocol (Not Checked)
NWLink NetBIOS
NWLINK IPX/SPX/NetBIOS Compatible Transport Protocol
Internet Protocol (TCP/IP)


This is what I have Installed on Windows 98SE

Client for Microsoft Networks
D-Link DFE-530TX+PCI Adapter
NetBEUI
TCP/IP
File & Printer Sharing for Microsoft Networks

We want to be able to connect to the Internet & share files.

We can connect to the Internet with either or both computers.

We can see the shared files on the WinXP from Win 98SE but we cannot see the files on Win 98SE from WinXP. We get the error message as we posted before.
We can ping both computers.

Thanks.

 

LDTate - I have to take issue with your post.

First, all the main Microsoft network protocols (TCP/IP, IPX/SPX, NetBUEI) allow you to resolve names over the network. They use NetBIOS to do this. NetBIOS is a higher level protocol suite that runs over the top of the other protocols. NetBIOS is NOT the same as NetBUEI!

NetBUEI works totally by broadcast, and not just layer 2 broadcasts, but layer 3 too. I won't go into the details of that, but the effect is that the Network card cannot distinguish between packets sent for its PC and those sent to any other PC on the network. All packets sent over the network have to be processed by the central CPU on every PC on the network. That means if you send a 1Gb file to the PC next to you, every computer on the network slows down. That is because every computer has to receive all the data and decide whether or not it is for them.

With other protocol suites many broadcasts can be handled by the network card without involving the central CPU.

The braodcasts also negate the advantages of a switch over a hub. Because all the NetBUEI traffic is broadcast, the switch (which works at layers 1 and 2) cannot determine which PC the packet is intend for and it falls back on its default behaviour of flooding (send to everyone) the network. On a NetBUEI network a switch will be SLOWER than a hub, because the switch has to first check the packet and then decide it needs to Flood the network. A hub just sends it to everyone straight away.

So NetBUEI is a poor protocol suite to choose.

Network protocols are analogous to spoken languages; languages being verbal communication protocols after all. Installing multiple protocol suites is akin to trying to communicate in a room where two or more languages are being spoken. It's noisy and inefficient.

Nowadays you will have to work very hard to find a print server that will use IPX/SPX and not TCP/IP. Very few manufactures would be stupid enough to cut themselves out of such a large share of the market. The only likely place where you may have to run IPX/SPX is if you are on a Novell network (and even then many of them now run over TCP/IP).

As you need TCP/IP to communicate over the network and choosing between TCP/IP and IPX/SPX on technical grounds is a bit like choosing between swings and roundabouts, you might as well choose TCP/IP.

TCP/IP will allow you to do anything you want to do over a network. It is fairly straight forward to set up once you understand the basic rules of IP addressing. It is robust and there are plenty of tools available to help you manage it.

Use TCP/IP on its own to get the best from your network unless you have a very good reason not to.

 

Hi,
Some more info on our continuing problem:

Not only can we not see the WIN 98 computer, our WIN XP computer does not show up in My Network Places. The only thing listed here is "Add Network Place ", "Network Setup Wizard" & "Entire Network ".

We found some further info in User Accounts regarding Networking as follows:

We can Ping the Win 98 Computer with both the computer name and IP Address.

When we type the following at the Command Prompt we get:

C:\>net view \\192.168.0.101 (This is IP Address of Win 98 Comp.)
The Workstation service has not been started.

More help is available by typing NET HELPMSG 2138.

C:\>NET HELPMSG 2138

The Workstation service has not been started.

EXPLANATION
You have tried to use the network before starting the
Workstation service.

ACTION
Start the Workstation service by typing:

NET START WORKSTATION

C:\>NET START WORKSTATION
System error 1058 has occurred.

The service cannot be started, either because it is disabled or because it has no enabled devices associated with it.

Does anyone know what this last system error means and how it can be corrected?

Thanks

 

ReggieB,
I agree and understand what you are saying. Sometimes what should work and what shouldn't, don't and do. Like my link to DLink.com Which is where my post came from. Another example is where I work, we have a few Snap drives. One should be able to attach to the Snap drives with just TCP/IP on your workstation. Unless you also have IPX on the workstations you won't see or be able to login to the Snap. Shouldn't be that way but it is. Besides what harm would it do to try adding IPX? One can always remove it if it doesn't help.

 

Just a thought, but didn't see it posted, besides just enabling file and print sharing on the 98SE, don't you also have to "share" something (file/folder) on the 98 machine for it to be seen?

Sorry, 2nd time around saw it, going to bed

 

LDTate,

Shall we agree on a compromise position: Ideally keep to TCP/IP, but don't be afraid to add IPX/SPX to overcome a particular problem.

I would also add that I did find one situation where I could find no alternative to using NetBUEI, and therefore installed it.

My main point would be not to install all the protocols as standard practice. I am confident that in most situations best practice is to keep to a TCP/IP only.

 

Just my 2 cents

I have found this to be very true in recent days

FIREDANCER

 

Hi TJ-IT,

Yes, we do have files/folders marked for sharing on both computers.

Thanks