M
MichaelMarch
This problem has been plagueing me for over a year now... and I have
yet to resolve it.
We use to run Windows 2000 on all our computers at the office and
connecting to a 2003 SBS server and everything was fine. Someone had
not used there computer in 4 days to connect to the file share, didn't
matter.. it would connect fine.
Since I've purchased and upgraded all the computers to Windows XP, I've
been plagued with time out problems. A few legacy computers which are
still running Windows 2000 connect with NO ISSUES.
Senario: If I was to not connect to any of the file shares for 2 hours
then my connection to the server would time out. Reconnecting via a
drive mapping or using the UNC name would cause the server to either
time out or Prompt for the user name and password. Even with typing in
the correct user name using DOMAIN\username convention it would come
back with invaild username or password. If I use the Administrator
Account username and password then the connection would be reconnected,
but now the user would be running as the Administrator! This hasen't
only effected file shares, it also effects the connection to the print
server too.. So everyone in the office is connecting via IP to the
printer and leaves me with no control over printer settings...
I've re-installed the SBS 2003 server on another computer and used
Windows 2000 to connect and everything is fine as soon as I connect
with a Windows XP computer the same problem will occure with in a few
hours. So this to me proves it's not a "server" problem rather then a
Windows XP problem.
I've installed Simple TCP/IP on both XP and the server and the problem
is still there.
I'm sure other people have come accross this issue before.
Networking Information:
10 users
Linksys Wireless Router, controls DNS, DHCP and is the default Gateway.
AD is used for user accounts
Everything is on the domain
Everything is licenced
The switch is a 24 port D-Link 10/100
DSL connection
All I want is a file and print to work!
Michael March
MCSE 2000/2003 and frustrated.
yet to resolve it.
We use to run Windows 2000 on all our computers at the office and
connecting to a 2003 SBS server and everything was fine. Someone had
not used there computer in 4 days to connect to the file share, didn't
matter.. it would connect fine.
Since I've purchased and upgraded all the computers to Windows XP, I've
been plagued with time out problems. A few legacy computers which are
still running Windows 2000 connect with NO ISSUES.
Senario: If I was to not connect to any of the file shares for 2 hours
then my connection to the server would time out. Reconnecting via a
drive mapping or using the UNC name would cause the server to either
time out or Prompt for the user name and password. Even with typing in
the correct user name using DOMAIN\username convention it would come
back with invaild username or password. If I use the Administrator
Account username and password then the connection would be reconnected,
but now the user would be running as the Administrator! This hasen't
only effected file shares, it also effects the connection to the print
server too.. So everyone in the office is connecting via IP to the
printer and leaves me with no control over printer settings...
I've re-installed the SBS 2003 server on another computer and used
Windows 2000 to connect and everything is fine as soon as I connect
with a Windows XP computer the same problem will occure with in a few
hours. So this to me proves it's not a "server" problem rather then a
Windows XP problem.
I've installed Simple TCP/IP on both XP and the server and the problem
is still there.
I'm sure other people have come accross this issue before.
Networking Information:
10 users
Linksys Wireless Router, controls DNS, DHCP and is the default Gateway.
AD is used for user accounts
Everything is on the domain
Everything is licenced
The switch is a 24 port D-Link 10/100
DSL connection
All I want is a file and print to work!
Michael March
MCSE 2000/2003 and frustrated.