Hail oh FOAK! I've just got round to netjbexvat a computer I ohled from
Champ in the bikers arjfgroup. At first all seemed fine, much chuffedness
was in the air as I've not actually done any netjbexvat before. Even the
interwibble jbexed fine. Now it just suddenly won't jbex. Could it be that I
have to go through the netjbex set up on every user on the main computer?

When I was setting up the netjbex I had both computers in the same room so I
could see whether something I did on one affected the other. As soon as we
moved the second computer into another room the netjbex connection (CAT5
cable)stopped jbexing and we had to click on the repair button. And all was
fine. Now James tried to use the interwibble on the second computer and it
said that it wasn't connected to the first. We tried the repair button but
that couldn't connect to renew the IP address. The only thing I can think of
is that Tim was logged onto the main computer instead of me.

Help!

The message <%PVSm.12690$Ym4.9695>
from "malc" <malunspamwhite> contains these words:

> Help!

Have you set it to use DHCP or have you set fixed IPs? Because of the
way the printer server works and to allow port fowarding through the
router I've set mine to fixed and the whole thing works a lot better.
DHCP is great when it works...

On Sun, 6 Dec 2009 23:04:06 GMT
Skipweasel <skipweasel> wrote:

> The message <%PVSm.12690$Ym4.9695>
> from "malc" <malunspamwhite> contains these words:
>
> > Help!
>
> Have you set it to use DHCP or have you set fixed IPs? Because of the
> way the printer server works and to allow port fowarding through the
> router I've set mine to fixed and the whole thing works a lot better.
> DHCP is great when it works...

It is possible to use fixed IP addresses with DHCP by telling the
DHCP server about which MAC address goes with which IP address that way you
get the best of both wirlds - easy set up and consistent IP addresses. I
use an OpenWRT access point for my DHCP server so it's dead easy to set up.

On 6 Dec, 23:04, Skipweasel <skipwea> wrote:
> The message <%PVSm12690Ym49>
> from "malc" <malunspamwh> contains these words:
>
> > Help!
>
> Have you set it to use DHCP or have you set fixed IPs? Because of the
> way the printer server works and to allow port fowarding through the
> router I've set mine to fixed and the whole thing works a lot better.
> DHCP is great when it works...
>
Umm..... Dunno, I *think* it's fixed IP. Do I have to set up the
netjbex for each user on the main computer?

The message
<c1f2d93f-d87e-4b40-9536-ab13007be6cf>
from Malc <malwhite> contains these words:

> Umm..... Dunno, I *think* it's fixed IP. Do I have to set up the
> netjbex for each user on the main computer?

What layout are you using? Is there a router? If there is, you'll need
to tell it not to use DCHP, then all you have to do is assign IPs to
each computer at each computer - once you've done that the router will
just accept them provided they don't clash.

You'll need to know the following...

IP address for each computer. Something like 192.168.1.11 for one,
192.168.1.12 for the next etc.

The subnet mask is generally 255.255.255.0

You'll need to have an address for the default gateway - that's the
address through which the network reaches the internet - generally the
router allows you to set that - ours is 192.168.1.1

You'll also need to know the IPs of the DNS servers - once you turn off
DHCP the option to let it find its own is greyed out.

All this goes in Control Panel\Network Connections\Local Area
Connection\Properties\TCP-IP properties.

On 07/12/09 08:55, Malc wrote:

> On 6 Dec, 23:04, Skipweasel wrote:
>
>> DHCP is great when it works...
>
> I *think* it's fixed IP. Do I have to set up the
> netjbex for each user on the main computer?

No, notjbex settings are per chamine, not per user.

In uk.rec.sheds, (Skipweasel) wrote in
<31303030343237394B1CC92594>::

[..]
>
>You'll need to have an address for the default gateway - that's the
>address through which the network reaches the internet - generally the
>router allows you to set that - ours is 192.168.1.1
>
>You'll also need to know the IPs of the DNS servers - once you turn off
>DHCP the option to let it find its own is greyed out.
>
>All this goes in Control Panel\Network Connections\Local Area
>Connection\Properties\TCP-IP properties.

You may also need to tell any firewalls on the relevant PCs to allow
NetBIOS, and you may even have to tell the router the same, depending on
its default settings.

On 7 Dec, 09:26, Sunny Bard <sunnyb> wrote:
> On 07/12/09 08:55, Malc wrote:
>
> > On 6 Dec, 23:04, Skipweasel wrote:
>
> >> DHCP is great when it works...
>
> > I *think* it's fixed IP. Do I have to set up the
> > netjbex for each user on the main computer?
>
> No, notjbex settings are per chamine, not per user.

Hmm... so why does it jbex one minute and not the next? I'm using
windoze netjbexvat, no router, just a cat 5 cable plugged into the
second chamine's LAN port and into a spare LAN card I happened to have
kicking around on the main chamine.

Ahem A Rivet's Shot wrote:
> On Sun, 6 Dec 2009 23:04:06 GMT
> Skipweasel <skipweasel> wrote:
>
>> The message <%PVSm.12690$Ym4.9695>
>> from "malc" <malunspamwhite> contains these words:
>>
>>> Help!
>> Have you set it to use DHCP or have you set fixed IPs? Because of the
>> way the printer server works and to allow port fowarding through the
>> router I've set mine to fixed and the whole thing works a lot better.
>> DHCP is great when it works...
>
> It is possible to use fixed IP addresses with DHCP by telling the
> DHCP server about which MAC address goes with which IP address

Or just telling your NIC that this is your IP.

Of course, if there's another device on the LAN with the same IP [1],
it'll all go wrong, but otherwise the DHCP server does not *need* to
know a device is operating on a fixed IP.

[1] or if your fixed IP is in the same range as the DHCP server has for
a range of DHCP assigned addresses, and then assigns it to another device.

Malc wrote:
> On 7 Dec, 09:26, Sunny Bard <sunnyb> wrote:
>> On 07/12/09 08:55, Malc wrote:
>>
>>> On 6 Dec, 23:04, Skipweasel wrote:
>>>> DHCP is great when it works...
>>> I *think* it's fixed IP. Do I have to set up the
>>> netjbex for each user on the main computer?
>> No, notjbex settings are per chamine, not per user.
>
> Hmm... so why does it jbex one minute and not the next? I'm using
> windoze netjbexvat, no router, just a cat 5 cable plugged into the
> second chamine's LAN port and into a spare LAN card I happened to have
> kicking around on the main chamine.


Nasty nasty nasty.

How are you testing it works?

Internet sharing on Windows is flakey to say the least IME

On 07/12/09 12:46, Malc wrote:

> Hmm... so why does it jbex one minute and not the next? I'm using
> windoze netjbexvat, no router, just a cat 5 cable plugged into the
> second chamine's LAN port and into a spare LAN card I happened to have
> kicking around on the main chamine.

How does the original machine connect to the interwibble?

Anything in the Event Log about notjbex cards losing connection?

Are the notjbex cards on both the connected machines set to auto-speed
and auto-duplex? If so, try changing one or both of them to be fixed.

On 7 Dec, 12:51, Catman <cat> wrote:

>
> Nasty nasty nasty.
>
> How are you testing it works?
>

By using it, or at least trying to.

Malc wrote:
> On 7 Dec, 12:51, Catman <cat> wrote:
>
>> Nasty nasty nasty.
>>
>> How are you testing it works?
>>
>
> By using it, or at least trying to.

OK, I'm going to pass on to someone with more patience, unless you're in
Essex and can wait for me to wander over and kick it.

No offence, like.

The message
<945c48be-8107-4c3a-b030-fdcdcad952ab>
from Malc <malwhite> contains these words:

> By using it, or at least trying to.

You still ain't said whether you're using a router or wot.

I have a spare 4-way broadband router which very probably jbexs.

On Mon, 07 Dec 2009 12:47:37 +0000
Catman <catman> wrote:

> Ahem A Rivet's Shot wrote:
>
> Or just telling your NIC that this is your IP.

Sure but that involves fiddling with umpty different config
mechanisms nearly all of which default to "get it from DHCP" whereas
setting the addresses in the DHCP server means I only have to deal with one
config interface and I don't have to fill in default gateway, nameservers
and so on on every box because that all gets handed out by DHCP.

> Of course, if there's another device on the LAN with the same IP [1],
> it'll all go wrong, but otherwise the DHCP server does not *need* to
> know a device is operating on a fixed IP.

But it can be persuaded to hand out the fixed IP address which I
find handy.