Printerserver inaccessible from RPC

Printerserver inaccessible from RPC

Post by Steve Joyc » Fri, 07 Mar 2008 01:25:14


I've had a stable network setup until recently, consisting of BT
router/modem, RPC, Windows PC, network storage box, printserver and a
wireless laptop.

The network part of my Unipod died, causing RPC boot sequence to hang
until unplugged from the network. After fiddling about with cables and
router ports, I bought a Net100 card (Unipod replacement n/a at the time).
Connectivity was restored but is now somewhat less stable - RPC will lose
connection to the internet (it dies quietly), whilst the windows systems
remain ok.

The real bummer, however, is that the RPC can no longer see the
printserver; all other devices, including the XP laptop, can be seen by
the RPC. The windows systems can see the printserver, as can VRPC running
on both systems.

I can't figure out why the RPC cannot see the printserver whilst it did
in the past. I can't be certain if it ever worked with the Net100 card,
but the loss of connectivity was noticed soon after it was installed.

Details: Router 192.168.1.1
RPC 192.168.1.2
W2K 192.168.1.3
Netbox 192.168.1.4
Dlink 192.168.1.10 (printserver)

RPC-SA running Adjust 4.39 (april 2004), with 96+2mb memory. DCHP only
used for the Laptop.

The Unipod is still plugged in - needed for CD drive and USB, but
reflashed without the EtherX module. Net100 has been reflashed with
latest EtherX version (no change). Changing IP address of the
printserver, but still in the 192.168.1 range, no difference. Exinfo
command doesn't show anything that looks like a problem, though I don't
understand all its output.

I'd intended to move to VRPC permanently, but issues with datestamp on
copied files has complicated the exercise - and I'd like to understand
what has gone wrong.

Any suggestions welcome
 
 
 

Printerserver inaccessible from RPC

Post by Alan Adam » Fri, 07 Mar 2008 02:00:43

In message < XXXX@XXXXX.COM >







It all depends on what you mean by "see".

Can you ping the address of the printserver? If not, check your
network settings - a network mask of 255.255.255.248 would cause the
printserver to be the only unreachable machine from the above list -
it says the network addresses are from 1 to 7.

If you can ping the printserver by address, then I'd use the address
in all connections - RISC OS isn't good at finding out Windows names
from broadcasts. Putting it in the RISC OS hosts file will look up the
address reliably (provided the address in the hosts file is correct -
have you checked that?) so that you can use names.







--
Alan Adams, from Northamptonshire
XXXX@XXXXX.COM
http://www.yqcomputer.com/

 
 
 

Printerserver inaccessible from RPC

Post by Steve Joyc » Fri, 07 Mar 2008 20:48:54

In article < XXXX@XXXXX.COM >,








Ping from the RPC to the printserver fails, either as 192.168.1.10 or by
name as in the hosts file. Netmask is 255.255.255.0 so should not be the
problem. Ping from the RPC works to all other addresses on the network,
either by number or name. The printserver will ping ok from Windows PC -
allowing me the option to change its address.

I did change the printserver address to 192.168.1.7 just in case values
above 7 were not being seen correctly - but behaviour remained the same.

The network section of the Unipod just might be interfering, even though
it appears disabled. Perhaps I should try the system with it removed.
Removal would be tiresome as USB and CD dependencies would have to be
disabled, at least temporarily.

Steve
 
 
 

Printerserver inaccessible from RPC

Post by Alan Adam » Sat, 08 Mar 2008 01:54:07

In message < XXXX@XXXXX.COM >












It makes me think of one router - Linksys? - which would not
communicate with any system which it had not supplied with a DHCP
address. It doesn't sound from your previous post as though this is
the behaviour however.

Can you watch the activity lights while pinging? It would be
interesting to know whether the ping is not being sent, or is being
sent and not replied to.

Can you (from the PC) connect to the printserver and see anything
about its clients, in the status pages? Ideally you would be able to
use arp -a, but that isn't likely to be provided.

It would be interesting to use arp -a at a * prompt on the RPC
immediately after pinging the address of the printserver.




I do vaguely remember some issues with multiple network cards and
EtherX, but I can't remember the details.






--
Alan Adams, from Northamptonshire
XXXX@XXXXX.COM
http://www.yqcomputer.com/
 
 
 

Printerserver inaccessible from RPC

Post by Steve Joyc » Sat, 08 Mar 2008 19:55:46

In article < XXXX@XXXXX.COM >,


Router is a BT Voyager, but that might be a re-badging job.

One of the lights pulses slowly - its certainly trying to do something.

Looking at the configuration page, UPnP (whatever that is) was enabled,
and the status page listed this against the RPC ip address. So, I tried
disabling it, having not a lot to lose.

RPC now pings the router as it used to do. I don't have a clue what UPnP
is - perhaps a some form of protocol - and what the consequences might be
having disabled it. The Windows PC can still dial in to its configuration
page, which sounds hopeful that the other computers are not adversely
affected.

This command did list the router/modem, lan disk and the printserver. Now
it only lists router and printserver, so more checks seem wise.

Many thanks,

Steve
 
 
 

Printerserver inaccessible from RPC

Post by Alan Adam » Sun, 09 Mar 2008 04:11:24

In message < XXXX@XXXXX.COM >







Universal Plug n Play. Not something likely to work with RISC OS.


I expect it will all work now.


arp only stores its information for 15 minutes. It should hold
information about any machine from which a packet has been received in
the last 15 minutes. If you ping them all, you should see them all.

Where it can get interesting is those occasions when ping fails, but
arp shows an entry. This normally means that a firewall, usually on
Windows, has blocked the ping reply. It doesn't block arp, which has
to happen first.

arp is the protocol used to get the ethernet address from the IP
address. The packet is then sent to the ethernet address.



--
Alan Adams, from Northamptonshire
XXXX@XXXXX.COM
http://www.yqcomputer.com/
 
 
 

Printerserver inaccessible from RPC

Post by Dave Higto » Sun, 09 Mar 2008 05:54:55

In message < XXXX@XXXXX.COM >



In principle there appears nothing to stop RISC OS supporting it.
The standards appear to be open and freely available. Connection
is via LAN.

Dave