Locating a new device on your network

I've been working with the Pogoplug recently, and realized that people may have difficulty locating a new device on their own network.

Most networked devices get an IP address dynamically, using DHCP. That is to say, the IP address of your net device could change on a regular basis. And you have no good way of knowing what it is.

Most of the time, this won't matter to you, but if you need to log in to a network device, you'll probably need to know the IP address.

To locate the IP address, first find the MAC hardware address. Just look at the bottom of your device, or on the label with your serial number. Usually, there will be a line for  the MAC hardware address, or it may be known as the device hardware address.. This will be in the format of 16 characters, in 8 pairs, separated by a colon (":") or a dash. The characters will be 0-9 and a-f. Write this down.

Now, you'll need to look at your DHCP server and look at the client leases. One of the leases will have the MAC hardware address of your Pogoplug listed. That entry will probably not have a name, but it will have an IP address. For an IPv4 address, the address will look like 4 numbers separated by dots, like 192.168.1.101 or something similar.

For most users, the DHCP server will probably be your router. Usually, the DHCP leases are listed in a table in the "status" section of your router's web interface. If you are not sure, just do a Google search on "router-name dhcp table".

If you don't have easy access to the router's DHCP table, you can use a brute-force approach. Download an IP address scanner (I use the older version of Angry IP Scanner) and have it scan your local network. This will have the affect of populating your ARP table (which is a list of all known devices). In Angry IP, you can also display the MAC address. Look for an entry that matches your device.

To make sure it IS really your device, try to ping the IP address. (Yes, Google it if you don't know how.) Once you have managed to ping the IP address successfully, examine your ARP table for the MAC hardware address. The command to type is "arp -a". If you find a MAC address in the ARP table that matches up to your device, you should have the right IP address.

Ran into an interesting Windows Server 2003 problem today. There was very high CPU utilization by lsass.exe and svchosts.exe (NETWORK SERVICE), and an inability to create outbound network connections. The client has previously rebooted this server to resolve the issue in the past, but wanted an explanation.

This client runs our application from that server using Terminal Services. Our application would not run and was given a cryptic message with the error code 10055. That five-digit code looked like a Microsoft TCP error to me, and sure enough it was. A quick Google searched turned this up:

10055 WSAENOBUFS -- No buffer space available.

Since that is a TCP error, that would mean no network resources are available. I ran "netstat -n" but saw very few established sockets.

Task Manager showed high CPU usage by lsass.exe and one svchosts.exe running as NETWORK SERVICE. I tried to download Process Explorer but Internet Explorer could not get to any websites; the bottom of the page said there was a DNS error.

I opened a command prompt (CMD) and was able to ping www.yahoo.com, so DNS works. I figured I would just FTP the file, so I ran FTP from their server to our web site and got another error:

> ftp: connect :No buffer space is supported

So, another error that points to TCP resources being unavailable.

I tried asking the great Google for answers about TCP resources and error 10055 but mostly found people who rebooted to make the problem go away. There were some Microsoft Articles about increasing the maximum TCP/IP socket buffers, but this is not our server, so I do not want to make changes requiring a reboot without knowing if it would even solve the problem.

Naturally, I examined Event Viewer and saw some error messages that suggested more socket errors which Microsoft's KB indicates a group policy not being able to execute. Probably not the root problem.

I decided to figure out which service was killing the CPU and see if it was also tying up the network resources.

LSASS sustains a bunch of services, including HTTP SSL, IPSEC, Kerberos, NetLogon, NT LM, Protected Storage, Security Accounts Manager, and maybe a couple others. It seems to manage TCP sockets rather than use them, so though CPU is high I figured I could safely ignore LSASS.EXE

OK, svchosts.exe is starts up services, so I ran the Services.MMC (or go to Control Panel > Administrative Tools > Services) to examine services. I went through all the listed services and looked at the details for each. Where the command line included svchosts.exe, I looked for the "-k NETWORK" to determine which svchosts.exe service was running as NETWORK SERVICE. I restarted each one and watched Task Manager to see if the high-CPU instance of svchosts.exe disappeared briefly. When I got to the "Server" service, both svchost.exe and lsass.exe freed up their resources. The Server service also restarted Net Logon, DFS, and Computer Browser.

Ta-dah! I was able to browse the web, FTP, and of course our application worked again. Since this was not our Windows Server 2003 machine, I passed the information along. But, that certainly beats rebooting completely.