xp and 98 file and print sharing

Have not worked much with networking xp as of yet but I now have a situation where I need to connect a win98 machine with xp. And to make matters worse the xp was built using ntfs. The 98 machine is fat32. Will they see each other and are there different settings with xp for file and print sharing different than other versions of windows.

Please give opinions.

 

I should start be saying, I don't use XP, I use win2K, but I can tell you that I successfully connect a ME(FAT32) with my 2K machine(NTFS). -=Actually it's running right now!=- That should not be a problem. And I can't see the file and print sharing to be much different from other wins.

 

gghartman -

The file systems would only matter if they were on the same physical machine. With networked PCs, it does not matter at all. And IMO (and for a variety of reasons) NTFS is a much better choice for machines that can run it.

XP is an NT system and does file sharing NT fashion. Quite a bit differently than non-NT systems.

If you are on a domain, you won't have to do anything. Otherwise, put a local user account on the XP system that exactly matches username and password in use on the 98 machine.

And be aware that the XP system may well be running a firewall so you will have to deal with that for the network connections to show you anything.

 

thanks for the information. it is appreciated.

 

Here's a nifty tip for XP boxes when it comes to filesharing and security-

Head into your administrative tools and choose 'Local Security Settings'

Of particular interest are all those listed under Local Policies/User Rights Assignment. The Security Options area is cool too, if'n you have 'dumb' users on the XP box as well as your own account.

 

try the following link http://www.practicallynetworked.com/sharing/xp/filesharing.htm

It has a mine of information and should tell you all that you need to know to get 98 to talk to XP.

 

Derek G - good article. Thanks for putting the link here.

This question from Eric by email. Thought I'd keep all the Q&A on the BBS since almost any question/problem one person has and posts about will be bothering lots of other folks as well.

First thing I'd try is removing all networking services from Computer3. Boot to safe mode, remove networking, remove the NIC from device manager. Then shut down and physically remove the NIC and boot back up. Then shut down again, insert the NIC (in a different slot if possible) and reload your networking services. Make sure you have gotten the latest drivers for the NIC.

If that doesn't fix it (or if you have networking questions in the future) here is additional information that would help.

1. XP Home or Pro?
2. Firewall in use? If so, the built in XP one or 3rd party (like ZA).
3. Protocols(s) in use?
4. Simple file sharing on the XP system enabled or not?

A few simple checks on the overall health of your network assuming you are running TCP/IP:

1. From Computer 1 - Ping computer 3 using the -t switch which will cause the ping to go on until you stop it with a CTRL-C. Also, use a larger packet size to stress the system just a little. You are looking to see if you get return times that are all pretty much the same and if you are getting time-outs. Example: start a command box (DOS window) and
ping -t -l 1024 computer3
Now try the same with computer2 and then the other possible combinations like pinging from computer3 to 1 & 2 then from 2 to 1 &

2. From computer1 do a net view for the other computers. If you see them, do net view /cache and see if the information returned is what you expect.

3. Run net statistics workstation and then again with server rather than workstation.

Please post back either with a "Eureka - it is fixed" or with more information.

 

Woof! The Newt has it!

Coupla questions I'd also ask if'n his ideas don't work, for further troubleshooting:

1) What kind of network are you running? I mean, is it just a buncha machines connected to a switch or a hub? Or is there a router involved? Are the machines all joining a workgroup or domain?

2) As someone stated earlier, the same user/pass on each machine is essential - because you're trying to connect TO a Win98 box, and not from, this shouldn't really matter, but still...

3) Is MS Inet Connection Sharing involved at all?

4) And, the most dreaded question for all IT people to ask: Are you running AOL on either of the afflicted machines? (Although AOL is technically a protocol on Win98 boxes, it's also much more in terms of the way it installs and binds to your NIC)

Anyway, just some more q's! Let us know if it all works out, and what fixed it.

 

Newt and DaddyBone - thanks for your numerous hints. Unfortunately, the problem still exists.
Just to answer some of DaddyBone's questions: this is several machines connected to each other by a simple network cable - no switch, no hub, no router. All the machines are joining the same workgroup.
MS Inet Sharing works fine - no problem with this. Further, NO AOL.
The pinging and also net view as suggested by Newt works fine - I can ping back and forth with success between all the machines.

One thing though that I realized only now is:
on computer 2 (the one to which I have access from computer 1) I open Network Neighborhood - Properties - Configuration - Ehternet Card - Properties - Bindings - and can see the following:
IPX/SPX compatible protocol -> Ethernet Card
NetBEUI -> Ethernet Card
TCP/IP -> Ethernet Card
all three entries have a checked box on the left side.

On computer 3 the situation is not exactly the same: it only shows:
IPX/SPX compatible protocol
NetBEUI
TCP/IP
there is also the checked box on the left side, but obviously no link shown to "Ethernet Card ".

When on computer 2 I go back to Network Neighborhood - Properties - Configuration and read the line TCP/IP; or the line NetBEUI; or the line IPX/SPX - there is always shown -> Ethernet Card right after the protocol name.
On computer 3 this is not the case.

I had configured computer 2 long time ago and do not remember how I managed to come up with this kind of configuration. I tried all kinds of things on computer 3 now to end up with the same entries as they are on computer 2, but I didn't make it.
Although, I have no idea whether this is the crucial thing to solve my problem or not.
All the settings on computer 1 (the XP machine) must be alright - otherwise I would not have access to the files on computer 2. Therefore, it seems clear that the solution must be with computer 3.
Any further ideas ?
Thanks in advance for all your help - Erich

 

Hehe, ok!

Next question - how do you have this set up without a switch or hub? Multiple NICs in the base machine, one for the WLAN, one for each of the Win98 boxes? An idea of how things are actually connected might give me some more ideas.

As for the -> Network Adapter part of your protocol listings, that's actually simply explained. At one time, the box that shows them in the list had more than one adapter in in, whether it be a true NIC or a virtual AOL or VPN connection or something else like that. Win9x uses the name of the adapter to show which one each protocol is bound to, in that case, and doesn't remove the appellation after the other adapter is removed.

One thought here, tho - even though you aren't on domain, or using a router, etc, each box should be set up with the same workgroup name. Win9x is terribly picky about connecting across workgroups, especially if a computer on a differently named workgroup is running a worgroup OS like NT, 2k or XP.

On to the next round!

 

hi you !
In the XP machine (base machine) there is a NIC for the LAN to the ISP, and another NIC for the "internal" network. Then there is 1 each NIC on each of the other 2 computers.
What concerns workgroup name: I've made absolutely sure that there is the same workgroup name for all 3 machines.
I don't know whether I've mentioned yet another detail:
when on the XP machine I open the windows explorer and go to the "Network neighborhood" and furhter to the name of the network, I can see both of the other machines in there. Unfortunately though, when I click on the name of computer3, it says that I have no rights to access any files there (whereas when I click on the name of computer2, the explorer opens up all the files I've granted access to).
All this is really very strange, inasmuch, as both computer2 and computer3 are Win98SE systems.
By now, I dout that the problem will ever be solved :-(

 

Erich - all these things have an explanation and a fix. Just that some are a tiny bit harder to track down than others.

You mentioned you are running all three of the common protocols. Why? If you have good IP connectivity the other two are just adding broadcast traffic for no real gain.

As for the specific problem, I'll have to think on this one some.

Can you directly map a connection from computer1 to computer3? Sometimes that works easier than trying the nethood thing which in my experience can be flakey at times.

If not, what is the exact error you are getting? Not only the pop-up one but also any event log errors that happen when you have a failure.

And DaddyBone - a hearty welcome to you.

 

Ok, hehe, one last try, based on something Newt said - bypass the 'hood and try going straight to your machine... in any address box, try using \\MachineName to tie into the recalcitrant machine. If this still gives you a no access error, try heading straight into the share, using \\MachineName\ShareName.

That's about all I can think of right now, except for removing all but the TCP/IP protocol on yer machines.

Good luck!


Oh, and, thanks for the welcome, Newt!

 

first my question to DaddyBone: I can't quite follow what you mean by saying "in any address box, try using \\MachineName... ".
Sorry, please explain to me in more detail what exactly I should do -
my question to Newt is similar: when you ask me "Can you directly map a connection from computer1 to computer3?" please tell me what exactly you mean by "directly map" - what do I have to do in order to try this out ?

Thanks for your patience and your extendes help -
fondest regards - Erich

 

On computer3, name a share. Lets use share3 for an example.

From computer1 using Windows Explorer, go to tools~map network drive and in the block for folder, put \\computer3\share3 and it should assign that share to a drive letter.

If you still get the access error when doing the above, there is another feature below the "folder" block to allow your connecting as another user. You can connect as if you were the admin of computer1.

DaddyBone's other suggestion has you doing the same thing but on a temporary basis by opening windows explorer on computer1 and putting \\computer3\share3 into the address line to see if it will open the folder for you.

BTW - information on which, if any, of the above work and what error(s) you get on any that do not work will help solve your problem.

BTW2 - this thread should give anyone reading it a good idea why it is better to post your issue on here rather than trying to work via email with any of the posters on the bbs. Lots more good ideas spring up this way.

 

The Newt has it! My suggestion was to just *try* and connect via UNC path - that's my first step, always, to see if things are working - if'n that works, the next choices are to either a) create a shortcut to that UNC path for ez double-clicking, or b) Newt's way to map the network drive.

 

Hi guys - unfortunately, none of the most recently suggested steps worked out. In each case, I have the window: Quote You have no access to computer3. Possibly, you don't have rights to use this network ressource. Contact the admin of this server to find out whether you have rights.
The time limit for Semaphore was reached. Unquote
Just to make sure once more I booted the Win98 System instead the WinXP from the same machine, and here all worked fine.
So, is the problem now with the XP on computer1 or with Win98 on Computer3. Don't forget though that I don't have the problem with the Win98 on computer2.
I guess I give up hoping that this will ever work.
Thanks anyway for all your help so far - fondly, Erich

 

Well.... if all else fails, reinstall!

If'n you REALLY want access to #3, I'd try reinstalling the OS - its a blunt-edge response to the problem, but 90% of the time it'll fix the pain...

 

Erich - sometimes good old DOS (or the app that NT systems use) will give you more useful information than the GUI.

Try this from computer1 and see what sort of error you get:

Net Use X \\computer3\share3 (where X can be any drive not already in use)

You might want to try it first to a share on computer2 just to make sure you have the syntax correct.

 

Hi Newt!

when I try doing in DOS what you said yields the following results (both for computer2 and computer3):

Quote
The Syntax of this command reads:
NET USE
[Device name \ * [\\Computer name\ ................
[/User: domain name\]user name]
[/User: punktuated domainname\]username]
[/User: domain name@punktuated domain name]
[/smartcard]
[/savecred]
[[/delete] [/persistent: {yes / no}]
NET USE {device name / *} [password / *] /HOME
NET USE [persistent: {yes / no}]
unquote

So, what does this mean ? Since I get to read the same kind of things when I perform this command for computer2 as well as for computer3, I guess the whole thing didn't show any crucial aspects now.
Please let me know. Many thanks - Erich