C
Christoph R.
Hallo,
this is my first post to this group, and I like to point that
my understanding of windows networking is rather
shallow.
I inherited a small company network of nine 2000 prof.
workstations and one 2000 server in a simple work group
setting. The server has an ICS connection (I also tested
with static ips, the regular dhcp, dns services are turned off).
The problem I am faced with is, that if almost all workstations are
connected the "late-comers" often don't connect correctly to my
work group - i.e. from a badly connected workstation I can't browse
the shares of other workstations, but Internet sharing always works
and I can ping and "see" the other workstations under my work group.
The "can't browse" expresses itself in hanging of the "Explorer" if
I click on an icon representing a work group member, this holds true
if I click on the icon representing the "badly connected
host workstation" itself.
The ladder phenomena is bi-directional in the sense that trying
to browse the shares of a "badly connected workstation" from
an otherwise correctly working workstation will also hang it's
explorer.
I try to solve this problem by rebuilding the server, replacing it
with XP prof. work station and googleed around for help - in
particular I toyed the registry setting described in
http://support.microsoft.com/?kbid=262963
with the effect that I still get the phenomena but unlike before
I don't get any entry in the event-log indicating a problem.
Here is an ad-hoc band-aid I came up with. If a workstation badly
connects to the network I disable the network adapter and reboot
it with the disabled network adapter, relogin and reenable the
network adapter and 98% every things works fine.
Any help with the matter would be greatly appreciated.
/Christoph
this is my first post to this group, and I like to point that
my understanding of windows networking is rather
shallow.
I inherited a small company network of nine 2000 prof.
workstations and one 2000 server in a simple work group
setting. The server has an ICS connection (I also tested
with static ips, the regular dhcp, dns services are turned off).
The problem I am faced with is, that if almost all workstations are
connected the "late-comers" often don't connect correctly to my
work group - i.e. from a badly connected workstation I can't browse
the shares of other workstations, but Internet sharing always works
and I can ping and "see" the other workstations under my work group.
The "can't browse" expresses itself in hanging of the "Explorer" if
I click on an icon representing a work group member, this holds true
if I click on the icon representing the "badly connected
host workstation" itself.
The ladder phenomena is bi-directional in the sense that trying
to browse the shares of a "badly connected workstation" from
an otherwise correctly working workstation will also hang it's
explorer.
I try to solve this problem by rebuilding the server, replacing it
with XP prof. work station and googleed around for help - in
particular I toyed the registry setting described in
http://support.microsoft.com/?kbid=262963
with the effect that I still get the phenomena but unlike before
I don't get any entry in the event-log indicating a problem.
Here is an ad-hoc band-aid I came up with. If a workstation badly
connects to the network I disable the network adapter and reboot
it with the disabled network adapter, relogin and reenable the
network adapter and 98% every things works fine.
Any help with the matter would be greatly appreciated.
/Christoph