Najprej hvala za zelo dober nasvet :)

Tukaj je moj log

[2006/06/28 17:21:52, 0] lib/util_sock.c:get_peer_addr(1225)  getpeername failed. Error was Transport endpoint is not connected
[2006/06/28 17:21:52, 0] lib/access.c:check_access(328) [2006/06/28 17:21:52, 0] lib/util_sock.c:get_peer_addr(1225)  getpeername failed. Error was Transport endpoint is not connected  Denied connection from  (0.0.0.0)
[2006/06/28 17:21:52, 1] smbd/process.c:process_smb(1187)
[2006/06/28 17:21:52, 0] lib/util_sock.c:get_peer_addr(1225)  getpeername failed. Error was Transport endpoint is not connected  Connection denied from 0.0.0.0
[2006/06/28 17:21:52, 0] lib/util_sock.c:write_data(557)  write_data: write failure in writing to client 192.168.1.121. Error Connection reset by peer
[2006/06/28 17:21:52, 0] lib/util_sock.c:send_smb(765)  Error writing 5 bytes to client. -1. (Connection reset by peer)
[2006/06/28 17:21:52, 2] smbd/server.c:exit_server(614)  Closing connections
[2006/06/28 17:21:52, 0] lib/util_sock.c:get_peer_addr(1225)  getpeername failed. Error was Transport endpoint is not connected
[2006/06/28 17:21:52, 0] lib/access.c:check_access(328)
[2006/06/28 17:21:52, 0] lib/util_sock.c:get_peer_addr(1225)  getpeername failed. Error was Transport endpoint is not connected  Denied connection from  (0.0.0.0)
[2006/06/28 17:21:52, 1] smbd/process.c:process_smb(1187)
[2006/06/28 17:21:52, 0] lib/util_sock.c:get_peer_addr(1225)  getpeername failed. Error was Transport endpoint is not connected  Connection denied from 0.0.0.0
[2006/06/28 17:21:52, 0] lib/util_sock.c:write_data(557)  write_data: write failure in writing to client 192.168.1.121. Error Connection reset by peer
[2006/06/28 17:21:52, 0] lib/util_sock.c:send_smb(765)  Error writing 5 bytes to client. -1. (Connection reset by peer)
[2006/06/28 17:21:52, 2] smbd/server.c:exit_server(614)  Closing connections

Nimam ideje zakaj  bi se to dogajalo na IP 192.168.1.121 ?!?!?!??!?!

Jernej Simončič wrote:
On Tuesday, June 27, 2006, 14:38:48, Ales wrote:

  
Torej omrezje A je trenutno, ki ze vsebuje PDC-a, omrezje B pa kamor je 
bil PDC-b streznik namenjen. Za cas konfiguracije sem PDC-b konektal v 
omrezje A (ki ze vsebuje PDC-a). Konfiguriral sem ga seveda za drugo 
domeno. Ali je torej možen vzrok, da se sedaj v omrezje A ne morem vec 
konektati v domeno zaradi omenjene konfiguracije? Zakaj
    

Ne, to ne bi smel biti problem (dokler imata PDCja različni imeni in
različna IPja). Vklopi na tvojem PDCju natančnejše logiranje, in glej kaj se
dogaja, ko se poizkusiš prijavit v domeno.

  


-- 
Aleš Curk :)

+ CALLTO://alescurk (Skype)
_______________________________________________
lugos-list mailing list
[email protected]
http://liste2.lugos.si/cgi-bin/mailman/listinfo/lugos-list

Одговори путем е-поште