I've noticed that the "findempeg" utility hasn't been working for me lately.

Finding empeg...

Trevor's Empeg/RioCar Finder v1.3 - Copyright 2002 - Trevor Man <trevors@email.address>

Searching for serial number 60000013
Host file: c:\win2k\system32\drivers\etc\hosts
Name to be give to empeg: empeg
Setting timeout to be 5 seconds.
No more replies. Giving up...

It worked just fine before. On multiple networks. Now, it's not working at all, on multiple networks with multiple addressing schemes.

Same computer, though, so I acknowledge it could be something about my computer. But I don't know what I could have changed to cause this.

Nothing seems to be wrong with the hosts file. I even removed the empeg line from the hosts file so all that was left was the localhost line. No change in behavior.

I notice that findemped *DOES* successfully find the Jupiter on my home network, just not the empeg.

Note: The empeg WORKS FINE on the lan and can be pinged and everything, web-browsed, FTP'd, everything, provided I look at its IP address on its front panel and use that instead of trying to use Findempeg to assign a name to it.

Any ideas?

Edit: removed tman's real email address

Does Emplode/jEmplode find the empeg? findempeg uses the same mechanism as Emplode to detect empegs on a network.

Yes, they find the empeg just fine. Interesting, huh?

Here's an idea. What if there were more than one ethernet adapter installed on the system. When I do ipconfig -all , there is a virtual adapter for my VPN connection. It's not trying to connect on *only* that adapter is it?

Yeah, that's it. When I disable the "sonicwall virual adapter", it finds the empeg instantly.

Hm. Wonder what to do about that. I need the VPN and I need the findempeg. How to make them coexist peacefully?

Yeah, OK, I've now got a batch file where it tries, in succession, broadcasting to

192.168.2.255
192.168.1.255
192.168.0.255

And then a fourth time with no broadcast address specified.

That works, and coexists peacefully with the second virtual network adapter.

Thanks for the help!

Great that you've managed to work around it. Does "findempeg -b192.168.255.255" work?

Don't suppose you can give me the output of "route print" can you?

C:\Program Files\Findempeg>findempeg -b192.168.255.255
Trevor's Empeg/RioCar Finder v1.3 - Copyright 2002 - Trevor Man <trevors@email.address>

Broadcasting to: 192.168.255.255
No more replies. Giving up...

C:\Program Files\Findempeg>route print
===========================================================================
Interface List
0x1 ........................... MS TCP Loopback interface
0x1000004 ...00 0c 6e 60 70 62 ...... 3Com Gigabit NIC (3C2000 Family)
0x2000002 ...00 60 73 e5 d8 94 ...... SonicWALL VPN Adapter
===========================================================================
===========================================================================
Active Routes:
Network Destination Netmask Gateway Interface Metric
0.0.0.0 0.0.0.0 192.168.2.2 192.168.2.240 1
127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1 1
192.168.2.0 255.255.255.0 192.168.2.240 192.168.2.240 1
192.168.2.240 255.255.255.255 127.0.0.1 127.0.0.1 1
192.168.2.255 255.255.255.255 192.168.2.240 192.168.2.240 1
224.0.0.0 224.0.0.0 192.168.2.240 192.168.2.240 1
255.255.255.255 255.255.255.255 192.168.2.240 192.168.2.240 1
Default Gateway: 192.168.2.2
===========================================================================
Persistent Routes:
None

Edit: removed tman's real email address

Wow. How helpful. The notion of the OS having a "primary" interface hurts my head.

Yeah, that's very interesting. I wonder why my ethernet card isn't considered the primary interface, and how I would go about setting that.

Route metrics, normally.

--Nathan

You probably can't. Most VPN clients have the ability to lock out non-VPN traffic ( a VPN server security option ). That's probably achieved by subjugating all the real interfaces.