[PROBLEMCHYLD]

I got it working. Most of the information from google is misleading, only a bit was accurate.

[jaclaz]

PROBLEMCHYLD, on 10 October 2012 - 01:34 AM, said:

I got it working. Most of the information from google is misleading, only a bit was accurate.

...and are you going to tell us HOW EXACTLY you made this happen, or if you prefer WHAT EXACT bit was the correct one and WHAT other bits are misleading?

jaclaz

[PROBLEMCHYLD]

jaclaz, on 10 October 2012 - 06:48 AM, said:

...and are you going to tell us HOW EXACTLY you made this happen, or if you prefer WHAT EXACT bit was the correct one and WHAT other bits are misleading?

jaclaz

Google is your friend. Its has all the answers, even if a lot of them are wrong. Just kidding I'll post step by step instructions later.

[submix8c]

On NT system:
* As UserAdmin, Define UserA with PwdA - log onto it once and log out (creates the Docs/Settings, etc)
* As, UserAdmin, make a SHARE and set UserA as one of users to access with whatever "rights"
On Win9x system
* "Client for Microsoft Networks" MUST be installed (in Control Panel->Network)
* AND used as "Primary Network Logon"
* AND UserA/PwdA as a User

(Somewhere) there will be a WorkGroup name - make sure they are the same. Also make sure the two connected PC's have the same Subnet defined AND that "auto detect" is set for IP so that the connections will "join" each other.

On Win9x, reboot and sign in as UserA/PwdA - don't have that user signed onto the NT system (can't sign on TWICE onto same PC).

EDIT! Post came afterward. Please let me know if what I posted matches what you did. It does work for me bi-directional.

This post has been edited by submix8c: 10 October 2012 - 09:51 AM

[PROBLEMCHYLD]

submix8c, on 10 October 2012 - 09:49 AM, said:

On Win9x system
* "Client for Microsoft Networks" MUST be installed (in Control Panel->Network)
* AND used as "Primary Network Logon"
* AND UserA/PwdA as a User

This is not mandatory. I used Client for Microsoft Networks and Windows Logon and they both worked.
Both directions was working for me. I even had Win 7 set to Send NTLMv2 response only. Refuse LM & NTLM and it was still working in both directions. I'm about to post the instrcutions. I was testing, making sure I got everything correct before I post. I don't want to give people the wrong instructions or information. @ submix8c, most of your instructions is needed so to you.

[PROBLEMCHYLD]

DSCLIENT.EXE Active Directory Client Extension and Client for Microsoft Networks is not needed for this procedure. You may use Client for Microsoft Networks if it suits you. To each their own

1. You want to have an Administrator account with a Password on the Win 7 computer.
2. You want to make sure all sharing options are enabled. Depending on what you are sharing, use your own discretion.
Right-click the folder you want to share. Click Properties --> Sharing --> Advanced Sharing.
Put a check mark on Share this folder. Click Permissions and set to your likings.
Click Apply --> OK ---> Apply --> OK ---> Close.
3. From the run box type SECPOL.MSC. In the Local Security Policy --> Security Options --> Network security: Lan Manager authentication level --> set to whatever security level suits you. There is no need to change registry values because once you change the security in Network security: Lan Manager authentication level, it is automatically changed in the registry.
4. On a Win98 machine, create a new user account with the same user name and password that is created on the Win 7 Administrator account. The Primary Network Logon does not matter.
5. Add this registry key, because without it, you will not be able to connect to Win 7. Reboot!

REGEDIT4

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA]
"LMCompatibility"=dword:00000003
;

6. Log-in to the new account you just created.
7. Network Neighborhood is not an option. In Windows Explorer, navigate to the desired shared folder on the Win 7 machine.

Example: \\Win 7 Computer name\The folder you to access
\\JohnDoe\Music

If someone can come up with a better way to explain these instructions incase I didn't simplify please do so. I will ask a mod to remove my post if someone decides to do it.

submix8c, on 10 October 2012 - 09:49 AM, said:

On Win9x, reboot and sign in as UserA/PwdA - don't have that user signed onto the NT system (can't sign on TWICE onto same PC).

Yes you can

This post has been edited by PROBLEMCHYLD: 10 October 2012 - 01:05 PM

[submix8c]

Huh!

LmCompatibilityLevel
LMCompatibility
A little "combo" info and here.

Maybe the method I used is the difference. I didn't do any of the other steps you provided, only what I posted, AFAICR.
98SE on VPC VM <-> Win7 Home Premium via the NIC's<->Router
(DSCLIENT, as you said, is for accessing AD Domains)

Oh well, whichever flies, proving it can be done, the main thing being you have to (generally) have matching setups (User+Pwd, Workgroup, TCP/IP, etc.) on both ends.
Win9x<->Vista/Win7/Win8(?)/(+Server varieties)

[PROBLEMCHYLD]

submix8c, on 11 October 2012 - 10:59 AM, said:

Oh well, whichever flies, proving it can be done, the main thing being you have to (generally) have matching setups (User+Pwd, Workgroup, TCP/IP, etc.) on both ends.
Win9x<->Vista/Win7/Win8(?)/(+Server varieties)

I agree, thats why most of your instructions was used. I was not able to connect until I added the registry key. See if you have the key on your Win98 machine and if you do delete it and try to connect again.

REGEDIT4

[HKEY_LOCAL_MACHINE\System\CurrentControlSet\Control\LSA]
"LMCompatibility"=dword:00000003
;

[PROBLEMCHYLD]

I can confirm DSCLIENT is needed if you are NOT using U98SESP3.x. I have tested this with and without SP3.x.
SP3.x installs the same updated files as DSCLIENT except for the Active Directory files.

[submix8c]

OK... I used AutoPatcher for my scenario, which undoubtedly(?) also has the necessary components that SESP has. Granted SESP goes beyond Autopatcher but I've been busy and haven't tested the latest SESP - the one I used was already in-place so...

[PROBLEMCHYLD]

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.

[submix8c]

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.

[JasonL]

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

This post has been edited by JasonL: 13 November 2012 - 10:48 AM

[JasonL]

deleted

This post has been edited by JasonL: 13 November 2012 - 10:48 AM

[submix8c]

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.

This post has been edited by submix8c: 13 November 2012 - 08:46 AM

[JasonL]

>> "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

This post has been edited by JasonL: 13 November 2012 - 09:42 AM

[submix8c]

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.

[submix8c]

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.micro...y/cc751488.aspx
Google

xp secure "guest account"

which includes a "discussion" of it here -
http://www.dslreport...t-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://devilsworksho...-ipc-problem/6/

This post has been edited by submix8c: 13 November 2012 - 10:56 AM