Hi,
Very odd one - see the end for the workaround I can't explain!
W2K SP4 + updates member server TS in NT4 domain.
W95 clients with original TS Client - conecting to TS via IP.
All been working for 5 years.
Last weekend did Windows updates and reboot (KB 929969 + Jan malacious software removal. Also got a message on reboot re registry size but when I looked, size is 52M and max size 100M.
Now some W95 clients are getting "Can not connect - server busy" message. Seems a bit random - reboot everything and different clients cannot connect.
TS has free licences and does not show any events when client attempts connection. XP RDP clients are fine.
Removed KB 929969 and increased registry to 125M - no different.
Tried creating a new TS connection on the client - that worked. Then tried deleting and re-creating the original - that did not.
And here is the bit I can't explain:-
Modifying the client connection to use the server Netbios name intead of IP works?????? Ping the Netbios name resolves to the correct IP so why won't it connect with the IP it has been using for the last 5 years!!!
Any ideas?
Very odd one - see the end for the workaround I can't explain!
W2K SP4 + updates member server TS in NT4 domain.
W95 clients with original TS Client - conecting to TS via IP.
All been working for 5 years.
Last weekend did Windows updates and reboot (KB 929969 + Jan malacious software removal. Also got a message on reboot re registry size but when I looked, size is 52M and max size 100M.
Now some W95 clients are getting "Can not connect - server busy" message. Seems a bit random - reboot everything and different clients cannot connect.
TS has free licences and does not show any events when client attempts connection. XP RDP clients are fine.
Removed KB 929969 and increased registry to 125M - no different.
Tried creating a new TS connection on the client - that worked. Then tried deleting and re-creating the original - that did not.
And here is the bit I can't explain:-
Modifying the client connection to use the server Netbios name intead of IP works?????? Ping the Netbios name resolves to the correct IP so why won't it connect with the IP it has been using for the last 5 years!!!
Any ideas?