• Announcements

    • xper

      MSFN Sponsorship and AdBlockers!   07/10/2016

      Dear members, MSFN is made available via subscriptions, donations and advertising revenue. The use of ad-blocking software hurts the site. Please disable ad-blocking software or set an exception for MSFN. Alternatively, become a site sponsor and ads will be disabled automatically and by subscribing you get other sponsor benefits.
KelvinTwister

Connecting a Windows 98 and Windows 7 through a network

60 posts in this topic

Its strange how Win 7 networking is. I guess there is no right or wrong way to get it working. I'm hoping to come up with an easy overall solution. I hate that we can't use Network Neighborhood for browsing. Maybe some hack can fix this issue.

0

Share this post


Link to post
Share on other sites

:wacko: How odd! Network Neighborhood is what I used. BUT I used MS Networking. Also (duh!) File and Printer Sharing, naturally (otherwise ->Win9x doesn't work) and Separate Users (naturally - MS Networking).

Some setting I missed?

No Vista/Win7 ATM, so can't fully retest. We'll keep "my" method "open" until I get a chance. UNLESS anyone else wants to do it. Otherwise, just use PROBLEMCHYLD's method.

0

Share this post


Link to post
Share on other sites

Deleted this post. Was redundant info and only p***ing off submix8c, prolemchylds method worked for me :)

Edited by JasonL
0

Share this post


Link to post
Share on other sites

deleted

Edited by JasonL
0

Share this post


Link to post
Share on other sites

Hate to tell you this, but the link given has absolutely no relationship to 2000/XP/2003, only Vista/Win7. There's absolutely no problem with those and have been using all three repeatedly and the method I give absolutely works. That's why I provided it for this topic as well.

edit - forgot to mention - you misunderstood the links "workgroup-name" - it DID mean "that-computers-name-in-workgroup" NOT the ACTUAL workgroup name. ;)

Edited by submix8c
0

Share this post


Link to post
Share on other sites

>> "Hate to tell you this, but the link given has absolutely no relationship to 2000/XP/2003, only Vista/Win7."

"This is for all the pals who got IPC$ Password Prompt while connecting a windows 95/98/ME machine to another windows 2000/XP/2003 machine in LAN, i.e. networking between NT & non-NT machine."

I'm no expert, I can only go on what's written ^

>> "you misunderstood the links "workgroup-name""

Ah yep, thanks. Anyone else not used to this stuff could make the same mistake I guess. If nothing else it might help them get it right too :)

Oh well, I got mine working, I'll leave the rest for the experts ;)

Edited by JasonL
0

Share this post


Link to post
Share on other sites

Pardon - you gave TWO links and the SECOND one is (pardon me but...) a STUPID idea. The GUEST account is NOT SECURE! Use MY method as given and you NEED NO insecure accesses! That's kind of like NOT putting a Password on the Administrator account.

0

Share this post


Link to post
Share on other sites

OK... I meant "Pardon Me - My Mistake - you have TWO links. I inadvertently referred to the wrong one.

Guest Account -

http://support.microsoft.com/kb/300489

http://technet.microsoft.com/en-us/library/cc751488.aspx

Google

xp secure "guest account"

which includes a "discussion" of it here -

http://www.dslreports.com/forum/r21583104-How-secure-is-the-Guest-account-in-XP-Pro-SP3

Please note that the Guest account is applicable "across the NT-OS board"...

ALSO note that NOWHERE does anyone suggest the tactics that you propose (via the link). It's not JUST an "opinion" but a general CONSENSUS.

You've already found that the correct info for the connection was already here (in spite of the links you provided, then finding you'd jumped the gun). Please also note the associate links I gave referring to PROBLEMCHYLD's posts (see post #47 and following...). The registry settings LOWER the security already, true? AGAIN, the method for 2K/XP/2K3 is SECURE (ref. ACL's)!

If you like, I'll restate it as EXTREMELY unwise. You're begging to be hacked... But, by all means, go ahead. ;)

???"deleted"??? Be that as it may... ...and not "p.sd off" - just presenting correct (AFAIK) information.

For the record -

http://devilsworkshop.org/tips/networking-windows-9598me-n-window-2000xp-lan-ipc-problem/6/

Edited by submix8c
0

Share this post


Link to post
Share on other sites

One tip I accidentally stumbled upon and that turned out to be the most important of them all: Win9x will not open a Win7 network computer directly; instead, one must know the exact names of the shares and access them directly.

For example, if the Win7 computer named TEST7 has a shared folder under the name of MyShare, then you'll have to type \\TEST7\MyShare in your file manager and it will open it.

I've wasted a lot of time searching around and trying all the tips I could find, until I found the above; as soon as I followed it, the shares became available.

As a mention, I'm only using Total Commander as file manager and as such, I locked a few Win7 shared tabs in one pane so they could be accessed when needed without having to type the share path again. ;)

I don't think it's been mentioned here but the Win9x machine(s) should have Active Directory Client (DSClient) installed.

 

this solution work for me

easy and simple

 

thank's

 

0

Share this post


Link to post
Share on other sites

I'm glad it works for you too. Welcome at MSFN! :)

0

Share this post


Link to post
Share on other sites

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!


Register a new account

Sign in

Already have an account? Sign in here.


Sign In Now

  • Recently Browsing   0 members

    No registered users viewing this page.