[jcifs] Problem connecting with domain controller

[Ingo Rockel]

Hi Mike,

thanx for the hint. But everything we tried with laddr didn't work. 
While trying to connect to the domain controller the following happens:

---< snip >---

No.     Time        Source                Destination           Protocol 
Info

     504 3.059597    10.21.22.41           10.243.50.22          TCP 
   30050 > 0 [SYN] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 TSV=168900049 
TSER=0 WS=0



Frame 504 (74 bytes on wire, 74 bytes captured)

Ethernet II, Src: 00:14:38:51:35:c8, Dst: 00:00:5e:00:01:06

Internet Protocol, Src Addr: 10.21.22.41 (10.21.22.41), Dst Addr: 
10.243.50.22 (10.243.50.22)

Transmission Control Protocol, Src Port: 30050 (30050), Dst Port: 0 (0), 
Seq: 0, Ack: 0, Len: 0

---< snip >---

the client send a SYN packet and doesn't get a response.

Because of the missing response, the client retries its syn-request:

---< snip >---

No.     Time        Source                Destination           Protocol 
Info

     545 6.051012    10.21.22.41           10.243.50.22          TCP 
   30050 > 0 [SYN] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 TSV=168900349 
TSER=0 WS=0

    1125 12.050435   10.21.22.41           10.243.50.22          TCP 
   30050 > 0 [SYN] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 TSV=168900949 
TSER=0 WS=0

    2979 24.049285   10.21.22.41           10.243.50.22          TCP 
   30050 > 0 [SYN] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 TSV=168902149 
TSER=0 WS=0

    5668 48.046985   10.21.22.41           10.243.50.22          TCP 
   30050 > 0 [SYN] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 TSV=168904549 
TSER=0 WS=0

    9305 96.042377   10.21.22.41           10.243.50.22          TCP 
   30050 > 0 [SYN] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 TSV=168909349 
TSER=0 WS=0

---< snip >---

In our test environment the authentication is successful and etherreal 
shows the following:

---< snip >---

No.     Time        Source                Destination           Protocol 
Info

     323 11.551613   10.11.13.106          10.11.13.165          TCP 
   46683 > 0 [SYN] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 TSV=508089462 
TSER=0 WS=0

     324 11.551862   10.11.13.165          10.11.13.106          TCP 
   0 > 46683 [RST, ACK] Seq=0 Ack=0 Win=0 Len=0

     325 11.552606   10.11.13.106          10.11.13.165          TCP 
   46684 > microsoft-ds [SYN] Seq=0 Ack=0 Win=5840 Len=0 MSS=1460 
TSV=508089462 TSER=0 WS=0

     326 11.552945   10.11.13.165          10.11.13.106          TCP 
   microsoft-ds > 46684 [SYN, ACK] Seq=0 Ack=1 Win=65535 Len=0 MSS=1460 
WS=0 TSV=0 TSER=0

     327 11.552973   10.11.13.106          10.11.13.165          TCP 
   46684 > microsoft-ds [ACK] Seq=1 Ack=1 Win=5840 Len=0 TSV=508089462 
TSER=0

     329 11.562428   10.11.13.106          10.11.13.165          SMB 
   Negotiate Protocol Request

     330 11.562800   10.11.13.165          10.11.13.106          SMB 
   Negotiate Protocol Response

     331 11.562834   10.11.13.106          10.11.13.165          TCP 
   46684 > microsoft-ds [ACK] Seq=52 Ack=112 Win=5840 Len=0 
TSV=508089463 TSER=156223790

     339 11.756665   10.11.13.106          10.11.13.165          SMB 
   Session Setup AndX Request, User: 
\cometuser123 at pool05.qm.pirobase.de; Tree Connect AndX, Path: 
\\pool05.qm.pirobase.de\IPC$

     340 11.763106   10.11.13.165          10.11.13.106          SMB 
   Session Setup AndX Response; Tree Connect AndX

     341 11.763155   10.11.13.106          10.11.13.165          TCP 
   46684 > microsoft-ds [ACK] Seq=338 Ack=262 Win=5840 Len=0 
TSV=508089483 TSER=156223792

---< snip >---

Any other ideas? Why is the SYN packet going to port 0 on the server 
side? What might block the SYN packet or the response to it?

Again, thanx for the help.

regards,

	Ingo

Michael B Allen schrieb:
> On Wed, 29 Mar 2006 12:24:36 +0200
> Ingo Rockel <irockel at pironet-ndh.com> wrote:
> 
>> of available domain controllers (seven), jcifs tries to connect to the 
>> first (in a different network) and fails with the following message:
>>
>> jcifs.smb.SmbException:
>> jcifs.util.transport.TransportException: Connection timeout
>>      Flags: 0x0002 (SYN)
>>
>> and this packet seems not to get any answer. It looks like a network 
>> problem to us but we don't have any idea what it might be in particular. 
>> Any Ideas or Hints welcome.
> 
> Failing to respond to a SYN packet means that the target address is
> routable but no one is listening at the other end. From your "in a
> different network" comment I would guess that you need to look at the
> laddr properties. All property descriptions are at the bottom of the
> overview page of the API documentation.
> 
> Mike
-- 
PIRONET NDH AG
Dipl. Inf. Ingo Rockel - Produktentwicklung
Maarweg 149-161, 50825 Koeln
Tel.: +49 (0)221-770-1788 / Fax: +49 (0)221-770-1005
mailto:irockel at pironet-ndh.com - http://www.pironet-ndh.com