• Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 456
  • Last Modified:

Windows 2003 Server with Windows 7 workstations

I have a Windows 2003 workgroup server with 6 user accounts.  I have 3 windows 7 Pro PC's and 3 XP Pro PC's also on the same workgroup with identical username and password setup 1 user account per PC.  I have no trouble mapping drives from XP PC's to the Windows 2003 server and brwosing the contents of the mapped drives.  Windows 7 users are able to create drive maps and browse the contents of mapped drives at first.  When they log off the Windows 7 PC and log back on to the same windows 7 PC, the mapped drives are extremely slow to come up and progrems located on the mapped drives are virtually useless.  They can remove the mapping, then remove the saved passwords from the credential manager, then re-map the same drives again.  At this point, the access speed is again very good.

I have at a loss to what's happning and any help would be greatly appreciated.  
0
rmurakami
Asked:
rmurakami
  • 6
  • 6
  • 2
  • +2
1 Solution
 
kevinhsiehCommented:
Why are you not using a domain? It would make things a lot easier.
0
 
rmurakamiAuthor Commented:
This setup is going out to a middle of nowhere and needs to be worked on by people that has never seen a domain.  I agree that a domain would be simpler at first, but if a serve crashes and no appropriate hardware could be found to replace the failed server, a workgroup server would be easier to replace.
0
 
Run5kCommented:
Based upon past experience, I think that you are encountering this problem:

http://support.microsoft.com/kb/297684
0
Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

 
bigmack333Commented:
Have you checked both workstation and server logs? Run "eventvwr.msc", any major errors or warnings?

How do your workstations resolve the server name? Is your Win2k3 server also the DNS server?

Please let us know what you find.
0
 
Run5kCommented:
In the event that doesn't work, I would try this next:

Windows 7 mapped drives disconnect with red X
0
 
rmurakamiAuthor Commented:
Run5k;  Its similar but not quite the same.  ther are no red X and the drive maps are still accesible.  They are just very slow to browse and access as if they are trying multipe authentication methods for each packets.  I will look into your second suggestion.

Bigmack333;  The server is configured as a dns server as well as WINS.  NETBIOS is turned on all the workstations and appears on the server's DNS and WINS entry  as a paticipant
0
 
smangognaCommented:
Try using a script that delete all mappings and maps drivers at logon
net use x: /del
net use x: \\share /y
you may put it on startup
0
 
rmurakamiAuthor Commented:
smanqoqna: Yes I tried it with script and no script.  the scrips runs just fine but the access to mapped drive contents after the script completes is still very slow.  The only way I got back the speed is also to delete the saved credentials before I remap.
0
 
smangognaCommented:
If you run net use /delete no map no credential
then you can use:  net use x: \\server\share /user:administrator password

so you give new credential in the script
0
 
rmurakamiAuthor Commented:
Smangogna:  Good though I will give it a go.

On another note.  If I disable the NIC and then immediately enable the NIC then the problem disappears until the nexrt reboot
0
 
Run5kCommented:
Did you find the time to test the second suggestion that I posted at http:#37035988 ?
0
 
rmurakamiAuthor Commented:
I found a workaround (Not a solution)  I incorporated a batch file as part of a startup script that stops and starts the network card as part of the login.  I am using devcon.exe (Command line utility from Microsoft that mimics device manager)  
0
 
Run5kCommented:
That's good to hear, but... did you find the time to test the second suggestion that I posted at http:#37035988 ?
0
 
rmurakamiAuthor Commented:
I've requested that this question be closed as follows:

Accepted answer: 0 points for rmurakami's comment http:/Q_27417704.html#37060178

for the following reason:

This workaround has been working for a month now
0
 
Run5kCommented:
It's nice to know that the author found a viable workaround, but my last two questions (that were actually the same one) went unanswered.
0
 
Run5kCommented:
Sounds good to me, Netminder.  Thanks for the feedback!
0

Featured Post

Get quick recovery of individual SharePoint items

Free tool – Veeam Explorer for Microsoft SharePoint, enables fast, easy restores of SharePoint sites, documents, libraries and lists — all with no agents to manage and no additional licenses to buy.

  • 6
  • 6
  • 2
  • +2
Tackle projects and never again get stuck behind a technical roadblock.
Join Now