long user profile login under Win95

Im with you on this, it should not take 30 min to login, unless!!!

What is your connection speed to the network?
On the users local profile do you have the same problem?

I would check to see the version of 95 that you are running under as thedifferent version's had many patches and hotfixes, you may be running under an Os with faulty (In Need OF fixing) software.

Good Luck!

DHCP/Wins configuration problem...?

Win95B wkst is attempting to run all apps and net connections from login script?, perhaps it has an incomplete lmhosts file or invalid reference to wins server. it is trying to build the lmhosts file on the runand at logon.

Check your wins server for keystoned entries...old entries which might reference network shares that may have undergone minute changes...

Search order for windows, when attempting to connect to network resources...

locally resolved machines/shares in cache
(netbios cahce.....nbtstat.exe)
Wins database...top to bottom,
lmhosts file on local machine
hosts file on local machine
browse master machine...

when the browse master is referenced, it forces that machine to resolve the requested network resource and pass it along to the requesting workstation...by a convoluted path
If browse master machine is in question, you might be undergoing a browse master election on your network...adding to the time taken to resolve netbios network resources..you can force a single machine on this network/segment in

network properties>file and printer sharing properties...

all of this takes a lot of network time....

mind you, windows networking is NETBIOS networking...and all is based on shared resources being broadcast to all available machines, and each machine is assumed to maintain it's own table of resolved network resources in cache or lmhosts or hosts file.

Incorrect entries in wins database will cause what you describe, especially when deploying a new wkst with no cache or lmhosts file, also bad wins address defined in tcp/ip properties will exacerbate this problem.

You have a new wkst browsing for it's resources problem on your network....

A.F.A.I.K roaming profiles only work on NT & 2000 systems, not on 9x.
When the user logs in on NT, it will get the profile from the romaing profile directory (server side stored), or create a new one if none was availaible.
Look for large Internet Cache content being loaded/saved (if not disabled from policies, this can easily accumulate to several hundred megs) and/or for .OST or .PST files created on the profiles directory structures.
Try disabling romaing for one user and see how thatcompares (to eliminate authentication and login type time-outs)
Run a network packet sniffer and see what traffic appears between the client and server. This will tell you if you have a name resolution, RCP or any other kind of problems.
Regards,
Radu