G
Guest
Hi y'all. Please don't interpret this persistence as pesty. I just REALLY
need an answer. Based on Chuck's posts, I'm hoping he might have something to
offer. I've done all the things his diag pages suggest and all seems fine,
but there's still
To repeat the post on 9/5...
....
I'm trying to solve an annoying problem with windows network neighborhood
browsing. The problem is VERY much like the problem described (and
eventually solved) i
http://www.microsoft.com/windowsxp/...-us-ms-winxp&lang=en&cr=US&sloc=en-us&m=1&p=1
under this forum. I found it by searching "slow network neighborhood
browsing" in this forum. Chuck, from Pchuck's Network blog, was very helpful
there. However, my problem still isn't solved.
The problem is the following:
Physical setup: The network has five computers (call them A,B,C,D,and E),
all of which run XP Pro, except for the new one (E), which has XP Home. For
the physical connections I have a DSL router with wireless capability. The
wireless portion of the network is only for one laptop. The rest are wired.
The DSL modem connects to a D-Link 8-port switch where all the wired
connections are concentrated.
Logical setup: All computers get addresses via DHCP from the DSL router,
and they are all part of the same workgroup. They all have windows firewall
on, with essentially the same settings. Nothing tricky here, just plug and
play basically. All the machines have password-enabled account
authentication.
Problem: Using network neighborhood from any machine, I can browse to the
workgroup and see all the machines. From machine E, I can click on ANY
machine, including E itself, and get immediate response showing all the
shares of the target. HOWEVER, from any one of A,B,C,D when I click on E, it
takes about 15-30 seconds to show the shared contents of the target.
So basically there's this delay when browsing TO computer E, but no delay to
any machine when browsing FROM computer E.
The computer E does show up in the root of My Network
Places on the other machines, AND when clicking the links provided there, I
get immediate response, both to directory contents browsing as well as file
open. This apparently has something to do with the "entire network" part of
the browsing process.
Following the advice of another post I started looking into the printer
update idea. It may be just another data
point, but when I browse (from any of A throug D) to the Printers & Faxes
folder under the computer E in Entire Network > Microsoft Windows Network >
(workgroup) > (computer E) > Printers and Faxes, I get a blank window after a
long pause. That is, it doesn't show the printers installed on E. But when
I browse (again, from any of A through D) to the P&F folders of any of the
other machines, it shows the printers and faxes installed on the remote
machine as expected.
Hmmm...
NOTES: I followed someone's advice in the above post and opened port 135,
which seemed to help a little. But there's still an annoying delay. I
wouldn't be too worried about this, but the new computer (E) is destined to
be the central "server" for our office as soon as possible. That delay will
be a real hassle over and over again.
MANY THANKS FOR ANY HELP,
need an answer. Based on Chuck's posts, I'm hoping he might have something to
offer. I've done all the things his diag pages suggest and all seems fine,
but there's still
To repeat the post on 9/5...
....
I'm trying to solve an annoying problem with windows network neighborhood
browsing. The problem is VERY much like the problem described (and
eventually solved) i
http://www.microsoft.com/windowsxp/...-us-ms-winxp&lang=en&cr=US&sloc=en-us&m=1&p=1
under this forum. I found it by searching "slow network neighborhood
browsing" in this forum. Chuck, from Pchuck's Network blog, was very helpful
there. However, my problem still isn't solved.
The problem is the following:
Physical setup: The network has five computers (call them A,B,C,D,and E),
all of which run XP Pro, except for the new one (E), which has XP Home. For
the physical connections I have a DSL router with wireless capability. The
wireless portion of the network is only for one laptop. The rest are wired.
The DSL modem connects to a D-Link 8-port switch where all the wired
connections are concentrated.
Logical setup: All computers get addresses via DHCP from the DSL router,
and they are all part of the same workgroup. They all have windows firewall
on, with essentially the same settings. Nothing tricky here, just plug and
play basically. All the machines have password-enabled account
authentication.
Problem: Using network neighborhood from any machine, I can browse to the
workgroup and see all the machines. From machine E, I can click on ANY
machine, including E itself, and get immediate response showing all the
shares of the target. HOWEVER, from any one of A,B,C,D when I click on E, it
takes about 15-30 seconds to show the shared contents of the target.
So basically there's this delay when browsing TO computer E, but no delay to
any machine when browsing FROM computer E.
The computer E does show up in the root of My Network
Places on the other machines, AND when clicking the links provided there, I
get immediate response, both to directory contents browsing as well as file
open. This apparently has something to do with the "entire network" part of
the browsing process.
Following the advice of another post I started looking into the printer
update idea. It may be just another data
point, but when I browse (from any of A throug D) to the Printers & Faxes
folder under the computer E in Entire Network > Microsoft Windows Network >
(workgroup) > (computer E) > Printers and Faxes, I get a blank window after a
long pause. That is, it doesn't show the printers installed on E. But when
I browse (again, from any of A through D) to the P&F folders of any of the
other machines, it shows the printers and faxes installed on the remote
machine as expected.
Hmmm...
NOTES: I followed someone's advice in the above post and opened port 135,
which seemed to help a little. But there's still an annoying delay. I
wouldn't be too worried about this, but the new computer (E) is destined to
be the central "server" for our office as soon as possible. That delay will
be a real hassle over and over again.
MANY THANKS FOR ANY HELP,