My 'intranet' : Ping to test

Well. You have set up the RISC OS machine and the Windows for Workgroups machine. Both have been rebooted (do this now if you have any doubts), the correct software is loaded...
On Windows, this should be done automatically.
Under RISC OS, you'll want to load OmniClient and then smbserver. Because of the way the NetBIOS port 139 is handled, you cannot load Samba first. Load it after Omni.

In order to test that things are workings correctly, we shall use a piece of software called ping. This simply bounces a small amount of data off of the destination machine, and gives a time for the round trip. It is a useful tool on the Internet for checking if a site is up and what the typical delay is.
It is also very useful on your TCP/IP network to check that machines exist and are correctly set up.

Under RISC OS...

Open a taskwindow and type in ping <machine name> which would be

ping
momspc

for my setup... Image, 8K GIF

If the ping fails, then try again using the IP address (ie, ping 10.0.0.3). If that works then you'll need to alter your Hosts file. It is possible, depending upon your setup, that Argo's !Voyager decides to install its own (I suspect Fresco is the culprit).
It is wise, if you use Voyager, to set the required values in the file !Voyager.Stack.Files.Hosts.
You can check where your system is looking for its resources by typing:

  *Show InetDBase$Path

in a TaskWindow.

If the ping fails using both name and IP address, then try the following:

An obvious one - is the network cable plugged in?
Is it plugged in correctly?
Is the link good? Polarity correct?

Most RISC OS network cards have some method to verify correct operation. My i-cubed card provides the command "EHTest" to tell me what interface is in use and how it is operating.
You should switch on your RISC OS machine after your hub, as when you are using 10baseT, the combo cards may revert to 10base2 (BNC) operation if the 10baseT (RJ45) cable is not plugged in correctly. Again, the card's diagnostics should tell you which interface is in use.
Finally, most hubs should have indicators for the port operating correctly. On my hub, I can see right now that ports 1 and 3 and the AUI port are all functioning correctly.
Is the netmask on both machines set to 255.255.255.0?
Is the Hosts file (on either machine) correct? You didn't mis-type an IP address?
On the hub, you haven't accidentally got one of the port disable (it is called 'segment partitioning' on my unit) switches set on a port you are trying to use?

Now we know the RISC OS machine can see the PC, it is time to turn our attention to the PC. The PING utility was also supplied with the Windows TCP/IP pack, so we can make use of it. Image, 4K GIF

Again, if it fails by name, check your Hosts and LMHosts files (both in \Windows) and see if it will work by IP address.
If that fails too, try the suggestions provided above.