How are the networks configured? subnet mask, broadcast, routes, etc... what devices deliver dhcp, and what clients use it? How are the routers configured? Route/Bridge? My hunch... you need a static route for 192.168.2.x on the Linux box since it's default route probably points towards the internet. Or, put the static route on the main (other) router. That probably makes more sense... Just guessing though. -cfd On Sun, 2006-08-20 at 22:48 -0400, Bill Mills-Curran wrote:
On Sun, Aug 20, 2006 at 10:41:17PM -0400, Bill Mills-Curran wrote:
Date: Sun, 20 Aug 2006 22:41:17 -0400 From: Bill Mills-Curran <bill@mills-curran.net> To: Worcester Linux Users Group <wlug@wlug.org>, BLU Discuss <discuss@blu.org> Cc: Subject: router/printing problems Precedence: list
I have a home network with 2 routers.
My 192.168.2.x network has a couple of windows boxes (some wireless) behind a linkSys router. This network feeds to my 192.168.1.x network which connects to the internet through a second router. My linux box (samba print server) is on the 192.168.1.x network and has a static IP. I just moved to this setup when I got Verizon FIOS. (Their wireless router has poor range.)
Problem. Since moving, I can't print to the samba-served printer from the windows boxes. I have modified samba to accept connections from the 192.168.2.x machines. Here's my samba log for the machine that tries to print.
[2006/08/20 04:02:21, 1] smbd/server.c:open_sockets_smbd(353) Reloading services after SIGHUP [2006/08/20 22:17:10, 0] smbd/server.c:main(798) smbd version 3.0.14a-2 started. Copyright Andrew Tridgell and the Samba Team 1992-2004 [2006/08/20 22:27:29, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/cache/samba/printing/hp.tdb): rec_read bad magic 0xd9fee666 at offset=175296 [2006/08/20 22:28:09, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/cache/samba/printing/hp.tdb): rec_read bad magic 0xd9fee666 at offset=175296
Any suggestions?
TIA, Bill
-- This message has been scanned for viruses and dangerous content by MailScanner, and is believed to be clean.
_______________________________________________ Discuss mailing list Discuss@blu.org http://olduvai.blu.org/mailman/listinfo/discuss
The previous was the smbd.log. Here's the one for the client 192.168.1.153.log:
[2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected [2006/08/20 22:27:25, 0] lib/access.c:check_access(328) [2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected Denied connection from (0.0.0.0) [2006/08/20 22:27:25, 1] smbd/process.c:process_smb(1084) [2006/08/20 22:27:25, 0] lib/util_sock.c:get_peer_addr(1150) getpeername failed. Error was Transport endpoint is not connected Connection denied from 0.0.0.0 [2006/08/20 22:27:25, 0] lib/util_sock.c:write_socket_data(430) write_socket_data: write failure. Error = Connection reset by peer [2006/08/20 22:27:25, 0] lib/util_sock.c:write_socket(455) write_socket: Error writing 5 bytes to socket 24: ERRNO = Connection reset by peer [2006/08/20 22:27:25, 0] lib/util_sock.c:send_smb(647) Error writing 5 bytes to client. -1. (Connection reset by peer) [2006/08/20 22:28:32, 0] tdb/tdbutil.c:tdb_log(725) tdb(/var/cache/samba/printing/hp.tdb): rec_free_read bad magic 0x42424242 at offset=673736
Bill