Host Engineering Forum
General Category => NetEdit => Topic started by: Henryp on March 10, 2015, 04:37:36 PM
-
I have a few computers where netedit takes two minutes before it displays anything. What could cause a problem like this?
-
Does it take a long time if you hit the rescan button, or just on startup?
-
A rescan takes just as long, about two minutes.
-
Do those computers have anything like VPN adapters?
-
I still have this problem and now it is happening on more systems. The PCs are Windows 7 64 bit.
-
How many devices are on your network? Are any connected through VPNs?
-
About 48, does a second NIC card create a problem?
-
NetEdit first broadcasts a query for connected devices, then waits a second or two for them to answer. It then cycles through each device that answers and reads all of the general setup data of each. On Host's office network there's 30+ devices and that process takes about three or four seconds total. If Windows networking gums up the works by trying to connect through VPNs and such stuff, we've seen things hang up for a long time. Multiple NICs shouldn't be an issue, but you can use the Network->Adapter menu to choose which NIC to query.
About 90% of what's on our network is Do-more and most are running short programs, which means they will respond very fast. If you are mostly running DL with longer scan times, I'm sure that process is slower, but it seems unlikely that it would be that much slower.
From Task Manager, what does processor load look like? Wondering if something is hogging the CPU.
Once NetEdit is running, if you hit the Scan Network button does it take a super long time too?
-
Multiple NICs shouldn't be an issue, but you can use the Network->Adapter menu to choose which NIC to query.
Multiple NICs usually aren't an issue. It can be an issue when they have the same IP addressing and subnetting.
IE
Wired NIC @ 192.168.1.1 - 255.255.255.0
Wireless NIC @ 192.168.1.10 - 255.255.255.0
This can cause all sorts of craziness. It can get even crazier if you routinely plug and unplug wires from switches without power cycling the switch to clear the routing table.
-
It is not just one PC it happens on 4 or 5. Task manager shows no issues.