There are some frighteningly clever people on this board (of course; they're Empeg owners!), so can anyone help me with this?

I'd like to get my Empeg on the network at work. We're a small company, with a network of about 12 PCs at this site. We're also using thin Ethernet, so I can't just attach the Empeg to the hub with a Cat5 cable.

Would it be possible to install a second NIC in my own PC (dual-booting Win2K and NT4), connected to the Empeg with a cross-over Cat5 cable? If I did so, would the Empeg be visible over the network? Would I have to use a static IP-address, or could it use the office DHCP server?

I may be asking too much here, but it would be extremely cool to have DisplayServer running here! And don't ask me why the boss hasn't switched to 10BaseT yet...

Cheers,
Bryan.

Mark 2 #080000515
12GB Green (was Blue)
...and it's full!

You can set up your NT box to act as a router and make the empeg accessible from your network.

* Install the second NIC.
* Give it an IP address on a different subnet than that of your office network.
* Give the empeg an IP address on the same subnet as your second NIC.

At this point, you can use the empeg from your machine. Now for the good stuff -

* Set the default GW on the empeg to be the IP address of your second NIC.
* On your PC, go into TCP/IP properties, and check 'Enable IP Forwarding'.
* From a command prompt do 'route add' with the necessary parameters (if your not familiar with route, you can look at the command line help. If you still have problems, send me a private message on the BBS).

Anyone that you want to access the empeg will also need a static route set up.

Once the static routes are set up, anyone in the office should be able to access the empeg.



A couple of things to note -

the empeg won't be visible in network neighborhood without some hacking (installing Samba).

Use of the main network DHCP isn't possible, 'cause the empeg will be on a separate segment. You could run a small DHCP server on your machine and serve only the empeg's, but then you'd have to worry about how people on the main network would find out the IP address after it changes (ie, using dynamic name resolution). IMHO, in this case, a static IP would be easiest.

Hope this helps.



Bill B.
Mk.2 SN 080000183 - 38 GB / Green

Hello Bryan,

Follow this description!

http://www.elementkjournals.com/ntp/9912/ntp99c1.htm

Instead of a shared Internet Connection you can use a Empeg Connection!

bye

cm

another alternative is to use a small 10BaseT hub that also has a 10Base2 thinwire port to connect the empeg to your existing subnet. the hub would then act as a repeater/media converter. small hubs like this can easily be found for <$50.

this approach has a few advantages: you could take advantage of your existing DHCP, if you like; you wouldn't need a second NIC in your machine; and you would not need to make any routing changes on any workstations.

good luck,
--dan.

Yeah, he's right. The best way to go about it is with thinnet->10baseT conversion, either with a dedictated converter box or with a hub that's got both kinds of ports on it.

Doing an extra NIC in the PC would work, but it's a configuration hassle. The amount of time and hassle you save is easily worth the cost of the extra piece of hardware.

___________
Tony Fabris

yea.. we keep a couple of those small 5port hubs around.. I also have a pile of thin coax -> AUI trancivers in a box somewhere.. ick.. hate the stuff (100baseT is so cheap now)

12gig red mk2 -- 080000125

The amount of time and hassle you save is easily worth the cost of the extra piece of hardware.
and the ability to access the empeg when your PC is turned off or isn't functioning properly...

Frank van Gestel

What? That NEVER happens!

-Zeke

just say you weren't paying much attention...

Yes, I never have to re-boot my PC...

Thanks for the tips, everyone. I'll have to see what I can pick up.

Bryan.

Mark 2 #080000515
12GB Green (was Blue)
...and it's full!