i have server 2008 not R2 installed 32bit processor. i have windows 7 and xp on other hosts not on a domain nor is the server a domain server. the issue is when i connect from a windows 7 or xp pc to a shared drive on the server the connection gets disconnected either the open shared drive folder drops the connection and also my remote app Dameware that i connect to server 2008 with drops as well. not sure what the issue would be. when i am connected via unc path dameware will drop and vice versa is this a stack problem not sure.

Hello, Disable all security softwares on the server and update your NIC card drivers. Once done, check results. This posting is provided "AS IS" with no warranties or guarantees , and confers no rights. Microsoft Student Partner 2010 / 2011 Microsoft Certified Professional Microsoft Certified Systems Administrator: Security Microsoft Certified Systems Engineer: Security Microsoft Certified Technology Specialist: Windows Server 2008 Active Directory, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Network Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows Server 2008 Applications Infrastructure, Configuration Microsoft Certified Technology Specialist: Windows 7, Configuring Microsoft Certified Technology Specialist: Designing and Providing Volume Licensing Solutions to Large Organizations Microsoft Certified IT Professional: Enterprise Administrator Microsoft Certified IT Professional: Server Administrator Microsoft Certified Trainer

i tried doing that with the nic card windows cant find any drivers this server is an hp ml310 g3 kind of old. i only have clam AV on it.

also when i ping the server i guess because of ip 6 this is what i get between windows 7 ping and server 2008 Reply from fe80::8146:b524:50ac:3e7a%10: time=4ms Reply from fe80::8146:b524:50ac:3e7a%10: time=2ms Reply from fe80::8146:b524:50ac:3e7a%10: time=1ms Reply from fe80::8146:b524:50ac:3e7a%10: time=11ms is that normal.

that looks ok, but ping is a very simple test and doesn't always reveal all problems. (it is a good place to start) start with the easy troubleshooting first. are there errors etc in event logs on server & client machines? have you confirmed the physical cabling/switch/router is not at fault (swap one thing at a time with a *known* good item) Don