A
Adrian Robertson
Hi Guys,
Have a site where all PCs have just recently been upgraded to Windows 2000
Pro. They are all sitting within a workgroup, not a domain.
There are 10 PCs in total, including a PC which will be the "server" (merely
a central repository for documents that gets backed up). Now as there is no
Windows 2000 Server on site, I am aware that there can only be a maximum of
9 or 10 connections to this server PC.
The problem I am having, is that one particular PC seems to be creating
multiple sessions (2 sessions), which is causing one other PC (the last one
to log on) to not be able to map a drive. What I have noticed in the session
information, is that the PC is in one session the Computer Name comes up as
the actual PC name (eg. Computer 2) but in another session, it comes up as
the IP address. All other PCs get listed as their IP address.
The second session (where the actual Computer Name shows) seems to be the
2nd session. Has anyone seen this and perhaps have any suggestions how I can
stop this 2nd session from occuring?
Whilst I am able to manually close the 2nd session, it would obviously be a
lot better for me (and them) to not have it occur n the first place,
especially as I am 1000km away from them!
Let me know if any more info is required ...
Thanks
Adrian Robertson
Have a site where all PCs have just recently been upgraded to Windows 2000
Pro. They are all sitting within a workgroup, not a domain.
There are 10 PCs in total, including a PC which will be the "server" (merely
a central repository for documents that gets backed up). Now as there is no
Windows 2000 Server on site, I am aware that there can only be a maximum of
9 or 10 connections to this server PC.
The problem I am having, is that one particular PC seems to be creating
multiple sessions (2 sessions), which is causing one other PC (the last one
to log on) to not be able to map a drive. What I have noticed in the session
information, is that the PC is in one session the Computer Name comes up as
the actual PC name (eg. Computer 2) but in another session, it comes up as
the IP address. All other PCs get listed as their IP address.
The second session (where the actual Computer Name shows) seems to be the
2nd session. Has anyone seen this and perhaps have any suggestions how I can
stop this 2nd session from occuring?
Whilst I am able to manually close the 2nd session, it would obviously be a
lot better for me (and them) to not have it occur n the first place,
especially as I am 1000km away from them!
Let me know if any more info is required ...
Thanks
Adrian Robertson