Logical Network Problems. Security Problems. Network Components and Services. Browser Problems. File Sharing and Permissions Problems.
Virtual Private Networking. Identifying the Scope of the Problem. Asking For Help. So what are the differences between this article, and Troubleshooting Internet Service Problems? Well, there is good new, and bad news. The bad news - there are a lot more network details that you will have to deal with. Since then, the server that you're trying to access could have been: Turned off. Disconnected, intentionally or unintentionally.
Moved out of range, if on a wireless LAN. Make sure that you don't have a simple physical network problem. And make sure that all computers are directly connected, on the same LAN segment , if at all possible. Try and diagnose physical network problems from the bottom up. This is usually one of the last things tried, but can be one of the easiest. If you're unfamiliar with IP configurations and networking, ask for help. Are all of the computers on the same subnet, physically and logically? Or did you, for some reason, setup a LAN with 2 routers?
An inappropriate Node Type will prevent name resolution, or slow it down. A problem in the Hosts or LMHosts file can have the same effect. Name resolution configuration is just one of the possible causes. Most of these instructions are written to focus on the needs of workgroup infrastructures, though domains also apply in most cases. If you're using directly hosted SMBs, consider the needs of domain based name resolution.
A misconfigured or misbehaving personal firewall, on a computer, can block access to the server that it's protecting. If you disable your personal firewall, and the problems stop, then you at least know where to start working. But if the problems don't stop, don't assume that the firewall is not the problem.
Many personal firewalls do not react properly to being disabled, and will continue to cause problems after being disabled. And look for a previously overlooked firewall, such as one bundled with your antivirus protection. There could even be a hardware firewall, sitting inside your computer. The nVidia nForce is probably the first, but surely not the last, device of this type. Misbehaving and misconfigured firewalls, and overlooked firewalls, are probably the most common root cause of problems with Windows Networking, in the cases where I have been able to provide assistance.
Depending upon the role played by any computer, it may require some, or all, of these components and services , to work properly. If you add or change any network components, run the Network Setup Wizard before continuing.
Make this setting consistent across your entire LAN. If your LAN Has a domain. Uses DNS, properly setup , for name resolution. You certainly should not need both.
You must remove IPV6 , at least to diagnose the problem. At least one computer must be running the browser service, but having too many browsers can result in a browser conflict. A master browser conflict can cause various problems in Network Neighborhood.
A master browser conflict can have numerous causes. Running Browstat is a good way to start looking for browser related problems. Servers with no shares don't get enumerated by the browser, so they won't be seen in Network Neighborhood. No, we don't need the phones on the list. We can't do exactly as you suggest, because the phones require DHCP to initialize, and needs a free address on the default VLAN, albeit just for a few seconds.
We have so many networked devices that sometimes the DHCP Server would not have an address to give the phone when it first initialized. Since most offices have just one network drop and desktops plug into a switch in the phone, when we changed the default VLAN for the phone ports one for each floor , it became the default VLAN for the desktops.
The devices that we can't see are still on the original VLAN 1. This is not a big problem, since the majority of our desktops are still Win XP, but I'd like to solve it if possible. You should be fine. This way, you can have your cake and eat it too.
The phones stay in their own VLAN and everything else is segregated into their own VLAN, all connected to the same physical port a la the physical limitation of one drop at each location.
There are some prety good whitepapers out there that describe the process in detail, especially any documentation you have for your switches. But I cannot find other computers in My Network Neighborhood. Click Networking on the navigation pane, and then select the physical network adapter, and then click OK. Verify that you use the correct workgroup name. Click System.
On the Computer Name tab, click Change. Make sure that the workgroup name is same as the workgroup name for all the computers on your network. If not, change the workgroup name. Next verify that the IP address is in the same network segment. Click Start , and then click Control Panel. Click Network Connections. Right-click Local Area Connection , and then click Properties.
Manually set the IP address from the same network segment, and then click OK.
0コメント