Any reason why Findempeg would quit working?

Posted by: tfabris

Any reason why Findempeg would quit working? - 07/06/2005 18:54

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 <[email protected]>

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
Posted by: tman

Re: Any reason why Findempeg would quit working? - 07/06/2005 19:13

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

Re: Any reason why Findempeg would quit working? - 07/06/2005 19:17

Yes, they find the empeg just fine. Interesting, huh?
Posted by: tman

Re: Any reason why Findempeg would quit working? - 07/06/2005 19:39

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

Yeah. Very odd. It's not blocked by firewall software is it?

What happens if you do "findempeg -b<ip of the empeg>" so for example "findempeg -b192.168.1.150"?
Posted by: tfabris

Re: Any reason why Findempeg would quit working? - 07/06/2005 19:45

Quote:
It's not blocked by firewall software is it?

No personal firewall software running on this box. Both the empeg and this computer are on the 192.168.2.xxx subnet within the hardware firewall. No other hardware between the PC and the empeg other than a 10/100 switch.

Quote:
What happens if you do "findempeg -b<ip of the empeg>" so for example "findempeg -b192.168.1.150"?

Finds it just fine. Instantly.

Of course, having the address ahead of time defeats the purpose.
Posted by: tfabris

Re: Any reason why Findempeg would quit working? - 07/06/2005 19:47

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?
Posted by: tman

Re: Any reason why Findempeg would quit working? - 07/06/2005 19:48

Quote:
Of course, having the address ahead of time defeats the purpose.

Obviously Just wanted to check that there wasn't anything blocking it. Try "findempeg -b192.168.2.255" ?
Posted by: tfabris

Re: Any reason why Findempeg would quit working? - 07/06/2005 19:52

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?
Posted by: tfabris

Re: Any reason why Findempeg would quit working? - 07/06/2005 19:55

Quote:
Try "findempeg -b192.168.2.255" ?

That works, too.

So I could theoretically do multiple findempegs in a batch file, for the netmasks on which I commonly use the empeg.
Posted by: tfabris

Re: Any reason why Findempeg would quit working? - 07/06/2005 20:00

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!
Posted by: tman

Re: Any reason why Findempeg would quit working? - 07/06/2005 20:08

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?
Posted by: tfabris

Re: Any reason why Findempeg would quit working? - 07/06/2005 20:10

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

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
Posted by: tman

Re: Any reason why Findempeg would quit working? - 07/06/2005 20:32

Quote:
C:\Program Files\Findempeg>findempeg -b192.168.255.255
Trevor's Empeg/RioCar Finder v1.3 - Copyright 2002 - Trevor Man <[email protected]>

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


Hrm. Nevermind. Was an idea anyway.

Is it always connected to the VPN? I had this problem originally. It would only send on the first adapter it comes around which has the correct route for it. In the end I simplified my network and it went away. Not sure how to fix it properly unfortunately.

Edit: removed tman's real email address
Posted by: tfabris

Re: Any reason why Findempeg would quit working? - 07/06/2005 20:41

Quote:
Is it always connected to the VPN?

No. The problem happens equally whether I am connected to the VPN or not. The virtual adapter is installed on the system even when the connection hasn't been dialed yet. When I temporarily disable that virtual adapter is when it works.
Posted by: peter

Re: Any reason why Findempeg would quit working? - 08/06/2005 07:44

Quote:
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.

This is another thread where the real answer is Knoppix. Windows behaves oddly and unhelpfully when you try and broadcast to the all-ones address: it sends packets out on all interfaces, but all with the source address set to that of the primary interface. Needless to say, no other networks' replies are then received. The only way to get sensible behaviour is to do exactly what your script does: send subnet-directed broadcasts to each accessible subnet in turn.

Peter
Posted by: wfaulk

Re: Any reason why Findempeg would quit working? - 08/06/2005 13:11

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

Re: Any reason why Findempeg would quit working? - 08/06/2005 14:13

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.
Posted by: Mataglap

Re: Any reason why Findempeg would quit working? - 08/06/2005 18:07

Route metrics, normally.

--Nathan
Posted by: genixia

Re: Any reason why Findempeg would quit working? - 19/06/2005 20:40

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.