Tek-Tips is the largest IT community on the Internet today!

Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!

  • Congratulations strongm on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!

New Xp can't see 98 with Linksys Router 2

Status
Not open for further replies.

Mainepcfixer

Instructor
Aug 23, 2004
2
US
Yesterday, I had 2 98 machines networked to see each other and each one has its own hardwire cat5 going to the linksys router attached to Verizons DSL Modem

Each machine has its independent connection to the internet, no ICS setup, and we could see each others files

Today, we got rid of one 98 machine, replaced it with the NEW XP home Dell laptop, went thru the Network Setup Wizard as directed, took the xp cd and did the same setup on the 98
NO SETTINGS ON THE ROUTER WERE TOUCHED EITHER TIME, DEFAULT FROM THE BOX

NOW, both machine still have access to the internet as expected, but the NEW XP can see the files on the 98, but cannot access them, even after I marked sharing on the whole 98 system, but the 98 can't even see the XP computer

I have removed norton Internet security and xp's built in firewall, shared the C drive and My documents and nothing shows up

one interesting note is that after 10 minutes, all of a sudden, when we first couldn't see the 98 machine, we blinked our eyes and there were the folders, restart the machine and we lose it until we play around again

Any ideas as to where to start?

JB
 
can they ping each other by ip?if yes, can they ping by name? what do you get if using net view \\remotepcname command?

Robert Lin, MS-MVP, MCSE & CNE
Windows, Network, Internet, VPN, Routing and How to at
 
the new laptop,is it ntfs partition? win98 can't see them. xp can see both ntfs,and fat32.

I shall use google before asking stupid questions!
 
erm thats not quite correct. Thats correct if its on the local harddrive, but the network access go through the operating system first, so the 98 read would hit XP which would then read NTFS

Now onto a horrible topic, Microsoft peer to peer networking.

Quick Synopsis:
Computer boots.
Looks on network.
Sees other windows machines.
An ownership auction begins to see who is going to run the network, this takes a while which is why you will experience a consierable delay before seeing any computers in my network places (this should be simplified as WinXP will win over 98).
Things work.

Now check in this order:
Network IP settings? if manual check both subnet and mask, if automatic you should be able to query the router to see who has DHCP licenses and see what ip's they have.

PING should work in both directions.

Check that they both have 'Client for Microsoft Networks' and 'File and printer sharing'

If that lot checks out then we shall look at the security settings.

Matthew







The Universe: God's novelty screensaver?
 
Matthew,

You were absolutely RIGHT on this one. I knew the info on NOT seeing NTSF was not correct, as I've used it in the past this way.

The delay you spoke about was 2:45 seconds, much longer than I was waiting and while eating supper, I smelled smoke in the Win98 room,.... power supply burnt out and thats what was causing such a long delay. I had experienced a few other problems the

New supply and all works fine, everything shows in 10 seconds

Thanks for everything and for the CORRECT evaluation on this

John
 
That NTFS read by 98 is interesting.

So what your saying is that if the OS is 98/2000/xp and the slave _local_ hard drive is NTFS, 98 wont read it. But if the drive is being read across the network physically on another box, it will read the NTFS drive?

You learn something everyday, thanks for the info and clarification on this.

PS Sorry to thread jack
 
If the NTFS filestore drive is mounted in a Win2k or XP box, and shared accross the network, andy Win9x or higher client can access the files.
 
Status
Not open for further replies.

Part and Inventory Search

Sponsor

Back
Top