can't view network in win98

Hi everyone!

I'm studying IT at a technical college and we've just started playing with networks. I thought I might have a bit of a play with it at home. I've got one system running XP Home, and one running Win98.

First of all, I thought I might try to connect my broadband up on the 98 machine. My broadband connects as a LAN through an ADSL router. This was no sweat, 98 automatically got addresses, it's already running TCP/IP. Terrific.

So I tried setting up a LAN with the 98 machine and the XP machine, I set static IP Addresses set sharing. The thing is I can see both computers on the network on the XP machine and browse the other computer's shared folder, but when I click on the Entire Network icon in 98 I get a message to tell me it isn't accessible. The network is set up, I just can't browse it from the 98 machine.

As I say, I'm a bit of a newbie, so I'm probably missing something really obvious, just not quite sure what.

Any suggestions greatfully accepted.

Justin.

 

If you do have a Router, then why do you have to share the connection ? . Can't you set each machine to connect separately ?

I have a Linksys Router, Cable Internet, one XP Pro and 2 98SE, and each machine is 100% independent of the other.

BillyBob

 

Hi BillyBob and everyone else,

I probably didn't make myself clear, in as far as what I was trying to achieve.

It's not that I want to share an internet connection. Anyway I can't do that as my ADSL modem/router only has one port (it came free from my ISP) and both of my machines only have one nic each.

My intention is to create a simple network between the XP machine and the 98 machine, using a crossover cable.

Why you may ask? I just want to be able to do it the hard way!

So, my problem is that as far as the XP machine goes, I can see the 98 machine and explore the stuff I made shareable. But when I go into Network Neighbourhood on the 98 machine and I click on Entire Network I get the network not accessible error, so I can't see anything.

I've set static IP addresses in the TCP/IP properties on both machines.

Anyhow, all suggestions, lessons etc. greatfully received,

Justin.

 

That might just make the ( a lot of ) difference between you and I. By my Linkksys Router having 4 ports each unit has its own port. And my Modem is also separate.

Last evening all three machines were on with one of them being online and used by Nieces and Nephews for school work and using the printer. My Wife and I were playing Gribbage on the other two.

BillyBob

 

On your windows 98 desktop.

Right click on "Netwok Neibourhood" then click on "properties ".

Under tab "configuration"

Did you get "client for microsoft networks" on the list ? if not, then add it.

 

Myth: You must set the primary network logon to "Client for Microsoft Networks" to access a peer-to-peer network.

Fact: All peer-to-peer network functions are available using "Windows Logon" or "Microsoft Family Logon" as well as "Client for Microsoft Networks" as the primary network logon.
Explanation: Logging on to a Windows NT or Windows 2000 Server requires setting the primary network logon to "Client for Microsoft Networks ".

 

There are some tricks to mixed-windows-OS windows networking. Read carefully these notes by MS-MVP Steve Winograd: http://www.bcmaven.com/networking/faq.htm

Two good sites Steve mentions:

http://wown.com
http://www.practicallynetworked.com/sharing/xp/addxp.htm

.

 

One simple thing may be stopping you, and I had this problem networking a XPSP2 and 98SE machine. The 98SE machine will send a DHCP request from it's UDP Port 68 to UDP Port 67 on the XPSP2 machine. If it does not get through, the 98SE will not 'see' the XPSP2.
XPSP2's built-in firewall by default does not have an Exception for this. If you are using Windows Firewall, create an Exception for Port 67, click on UDP, then click on Change Scope, then click on (My subnet only.). This sets it up so the port is only open to your network.
I do not know if ZA is capable of this, I use an old rules based version of Kerio as my firewall.

 

markp62,

He is using static IP assingments on both machines.

But your thought brought me back to an earlier one. Why not
give both machines Internet Access as well as peer-to-peer networking?

Use the XP machine as an ICS Host. For this you will have to
give up the static IP assignments on both (you can workaround this, but dont).

http://www.practicallynetworked.com/sharing/xp_ics/
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q308006

 

Fixed it!

Hi everyone!

Well, I'm glad to say I finally fixed this issue, just this very moment. I am so excited I thought I would immediately post and tell you all about it. Yeah, I admit it, I'm a geek!

This problem has been bugging me for weeks. I had a physical connection, I could ping back and forwards, and I could see and browse the 98 machine from the XP machine. When I opened up Network Neighborhood on the 98 machine and clicked Entire Network, it told me the network was not accessible.

Knowing that there was actually a connection meant it wasn't hardware. I tried everything I knew, set static IP addresses, made sure everything was set to share. I did a bit of reading on the net on the problem and I realised the 98 machine was asking for a network password at startup. I was just clicking cancel and letting it load.I realised this may be the problem-if Windows 98 didn't think I was allowed to use the machine it probably wouldn't let me browse the network!

I had no idea what any of the passwords were, but I did some reading and came up with an idea. I went into Properties of Network Neighborhood on the 98 machine and changed the primary network logon to Windows Logon. I restarted the machine and just clicked cancel when prompted for a password. I opened DOS and searched for .PWL files and deleted my friend's password file. When I restarted it prompted me to set a password, but I just clicked cancel, so there was no password set. I restarted the machine again and this time Windows 98 started up without prompting for a password.

Bingo! This time when I clicked Entire network in Network Neighborhood I could see it!

Now I realise this is probably not that exciting for everyone else, but at the moment I'm studying Information Technology at a technical college, and this has been a really good opportunity to use the detective skills to solve a problem. A couple of months ago I would probably never have been able to fix this, so I'm quite pleased with myself.

Anyhow, thanks everyone for suggestions, and who knows, this info may help someone else.

Justin.