1.Problem Discovering Windows Workgroups and Computers
2.Vista Computers Don't Discover other Vista Computers
I have two new Vista Computers, both running Vista Home Premium 64 bit.
I am trying to setup sharing so that I can use the same printer and
share files. However, when I type in the other computers
'\\computername' (file://\\computername) into either of the two
computers search boxes it says 'Windows cannot access '\\computername''
(file://\\computername). Both computers have the same Network name and
have Network Discovery, File Sharing, Public Folder Sharing and Media
Sharing Turned on. The Computer w/ the Printer has Printer Sharing
turned on. Both Computers also have Link-Layer Topology Discovery
Mapper and Responder enabled. I can't figure out why they won't
recognize each other. My only guess is that my wireless router is not
allowing them to see each other. I have a home network connected to a
wired router that one of the computers and a Linksys wireless router are
connected to. The second computer passes through the Linksys wireless
router to get to my home network backbone. Any ideas?
3.Vista computer does not discover XP computers
I have 3 computers on a wireless LAN, a Vista laptop, an XP laptop, an XP
In IE click Network Neighborhood on the XP computers and they display and
can access shared files on the Vista laptop, and on each other. In IE click
Network on the Vista computer and all it shows is itself. All computers are
in same workgroup and since each XP computer sees all the others there seems
to be no firewall issue. On Vista computer, Network and Sharing Center >
View Full Map shows all three computers plus the router.
Seems like I've had similar problems in the past that self-resolved somehow.
Any suggestions greatly appreciated.
4.Easy way to discover device model via SNMP ?
I am writing a management software that would provide some
basic info about the device, monitor some preconfigured
variables etc. I was under the impression that detecting
a device model would be as easy as doing an snmp query
of a correct oid (entPhysicalModelName). Everything worked
great for all of my cats: 2900, 3500, 2950, 3750 series,
it worked great for 1760, 2801, 3745, 3825 routers.
But when it came down to 7200 and 3600 series it was unable
to detect the model. Doing an snmpget on entPhysicalModelName
for 7200 returned an empty string, doing an snmpawlk on
.22.214.171.124.126.96.36.199.188.8.131.52 also gave no results. Ok, lets
try entPhysicalName, still nothing, and finally entPhysicalDescr
gave some usable results. With aironet APs even more trouble
entPhysicalModelName.1 is set but all I can see there is
garbage ? entPhysicalName is set correctly tough. The real
question here is there an esay way (the one that would work
for all cisco gear, well IOS based at least) to discover
the device model using snmp ?
5.Discovering DHCP linux device
I have built a small linux machine that I take with me to work on
customer's sites, but one thing I would like is a way to detect the
machine on their network.
If I were the systems administrator there, I could go through the DHCP
server logs and find it. But I'm not, and it just seems a little
unprofessional to have to ask for help to find my own hardware.
I know I could sniff the traffic and look for DHCP transactions, but
this is (by and large) a one time event which means I have to be
watching while the thing comes online. And it is again a little
unprofessional as it is quite cumbersome to be poring through sniffer
data to find my own hardware.
What I would do is write a script with netcat that broadcasts the
device's presence periodically, and have another application on my
laptop to listen for these broadcasts. As long as we're on the same
LAN I should be able to detect those broadcasts, and then I will know
the IP to manage the machine.
I can create this script, but I'm posting this to see if there are any
linux projects already underway that meet my requirements. I know
that my NAS (Infrant) uses a similar approach to managing those
systems, so something like that would do the trick.
6. discovering the ip address of a device
7. no audio input device discovered when microphone jack is connected
8. Problems discovering devices on the LAN