"[ste parker]" <(E-Mail Removed)> wrote in message
news:(E-Mail Removed)...
> [ste parker] wrote:
> > Alex Fraser wrote:
> >>"[ste parker]" <(E-Mail Removed)> wrote in message
> >>news:(E-Mail Removed)...
[snip]
> >>>PC2 > ethernet > PC1 > wireless > ADSL router.
> >>
> >>Bridging should work. Perhaps this is the cause of the problem:
> >>http://support.microsoft.com/kb/302348
> >>
> >>If the router has the ability to add routes, you could use routing
> >>instead.
> >
> > Aha, thanks for that. Certainly sorted out the PC (wirelessley)
> > connected to the router, still trouble getting the other PC to work
> > with it though, got some sort of conflicting IP complaint.
> >
> > My router is a Netgear DG834G, it has a section where you can add
> > static routes, so I'm assuming I could do things that way? Looked a
> > bit bewildering....
>
> ....and now it's just started working fine for no apparent reason. Must
> have tried it too soon before it sorted itself out.
Glad you got it working (hope it stays that way).
For reference, the routing method really isn't too hard to set up; one
possibility:
Router:
Internal interface set to 192.168.0.1/255.255.255.0.
Route 192.168.1.0/255.255.255.0 gateway 192.168.0.2 (using internal
interface).
PC1:
IP routing enabled.
Wireless interface set to 192.168.0.2/255.255.255.0.
Wired interface set to 192.168.1.1/255.255.255.0.
Default gateway 192.168.0.1 (using wireless interface).
PC2:
Wired interface set to 192.168.1.2/255.255.255.0.
Default gateway 192.168.1.1.
(You /could/ use a DHCP server on PC1 to configure this.)
Alex