shares and incoming connections on XP pro

[Guest Tester]

HI there,

I have a windows XP Pro machine with 4 shares and 8 PCs with windows

2000 Pro having the shares mapped to them, using 4 windows login

accounts on a LAN and domain. These machines are on a remote subnet

with lower speed links to where the domain controllers reside.

1. I am getting "No more connections can be made to this remote

computer at this time because there are already as many connections as

this computer can accept" on XP sharing machine.

2. On the Windows 2000 Pro client machines I am getting Microsoft

Windows network: The local device name is already in use. This

connection has not been restored" when trying to access a share of the

XP machine.

When I am doing a "net session" command on XP machine I am only able

to see 4 or 5 machines connected to it so far from 10 [max inbound

connections].

Only thing that got changed I used to have a windows 2000 Pro having

the shares on and now it is XP Pro.

I started rebooting the XP machine daily.

What can I check?

Thank you, T

[Guest Tim Slattery]

Re: shares and incoming connections on XP pro

 

Tester <calinguga@netscape.net> wrote:

>When I am doing a "net session" command on XP machine I am only able

>to see 4 or 5 machines connected to it so far from 10 [max inbound

>connections].

 

But those four or five machines may have more than one connection

apiece.

>What can I check?

 

The basic problem is that XP is not a server system. Yes, it somewhat

arbitrary to make a price point for Microsoft, but that's the way

they've set it up.

 

--

Tim Slattery

MS MVP(Shell/User)

Slattery_T@bls.gov

http://members.cox.net/slatteryt

[Guest Tester]

Re: shares and incoming connections on XP pro

 

On Oct 1, 9:12 am, Tim Slattery <Slatter...@bls.gov> wrote:

> Tester <caling...@netscape.net> wrote:

> >When I am doing a "net session" command on XP machine I am only able

> >to see 4 or 5 machines connected to it so far from 10 [max inbound

> >connections].

>

> But those four or five machines may have more than one connection

> apiece.

>

> >What can I check?

>

> The basic problem is that XP is not a server system. Yes, it somewhat

> arbitrary to make a price point for Microsoft, but that's the way

> they've set it up.

>

> --

> Tim Slattery

> MS MVP(Shell/User)

> Slatter...@bls.govhttp://members.cox.net/slatteryt

 

Hi Tim,

Yes, some connecting machines have 2 "Opens" field from net session

command output, I thought it is per machine[ shares mapped per

machine] and is not by numbers of shares/printers mapped[i have 4

shared folders]. Should I disable something? I already removed admin

shares C$ and D$.

What is meant by a connection, connecting to one file, 2 files 2

connections? Thanks for helping me out, T

[Guest Tim Slattery]

Re: shares and incoming connections on XP pro

 

Tester <calinguga@netscape.net> wrote:

>What is meant by a connection, connecting to one file, 2 files 2

>connections? Thanks for helping me out, T

 

I think it means a connection to a share or a printer. So you can read

and write the files on a single share with one connection.

 

--

Tim Slattery

MS MVP(Shell/User)

Slattery_T@bls.gov

http://members.cox.net/slatteryt

[Guest Tester]

Re: shares and incoming connections on XP pro

 

On Oct 1, 4:03 pm, Tim Slattery <Slatter...@bls.gov> wrote:

> Tester <caling...@netscape.net> wrote:

> >What is meant by a connection, connecting to one file, 2 files 2

> >connections? Thanks for helping me out, T

>

> I think it means a connection to a share or a printer. So you can read

> and write the files on a single share with one connection.

>

> --

> Tim Slattery

> MS MVP(Shell/User)

> Slatter...@bls.govhttp://members.cox.net/slatteryt

 

Hi,

But why I did not get these errors before when I was serving these

shares from a W2K Pro machine which I just replaced with windows XP,

can someone explain? Thanks, T