IT Employment

Ask something
Discussion Locked

XP Pro with NT4 Domain

0 helpful
2 replies

by philldmc

Closed to new repliesThis discussion is closed. It stays readable, but it takes no new replies.

XP Pro...how will it run on a NT4.0 Domain? Does XP react will to Proxy2.0?

Has anyone tried this? Please let me know what you think?

2 replies

by thedge

I am using xp pro on a nt 4.0 domain, with some problems. My connection tends to "fall off" to the network although I am still able to get out through the gateway.

I don't know what triggers it to "fall off", but I can tell when it happens - my name under the start menu will change from my full name to a lower case first name only when my connection falls off.

I have been trying to fix this since November - reinstall, new network card, disjoined form network, etc. Please let me know if you have any suggestions.

Thank you.

by rvanhorn

Change disconnect timeout for network shares
You might have noticed that even when you're connected and logged on to the network, some or all of your mapped resources show a red X beside the icon, indicating they're disconnected. This occurs because Windows NT and Windows 2000 and XP use a default resource disconnect time of 15 minutes. This automatic disconnect enables the server to recover server resources from idle connections. To reconnect to the share fairly quickly, simply double-click the icon.
This automatic disconnect behavior applies to Windows 2000 Professional systems that share their resources, as well as Windows 2000 Server systems. On either type of system, you can view the current server settings, including the automaticdisconnect period, using the NET command. Open a command console and type the following command to view your current settings:

NET CONFIG SERVER

The Idle Session Time value indicates the automatic disconnect period. To change the value, use the NET command again, as follows:

NET CONFIG SERVER /AUTODISCONNECT:

In place of , specify the number of minutes you want Windows 2000 or XP to use for its idle disconnect timeout. Note that this value sets the amount of time thecomputer will allow idle connections to its resources before closing them, not the length of time you can have resources open on a remote computer. To disable automatic disconnect, set the value to -1.
I've used this in a NT 4.0 Environment withgreat sucess.

This discussion is closed to new replies.