System.Net.Socket and Linux Server

Thread view:

Enable EMail Alerts

Start New Thread

Thread rating:

Ralf Haenel - 20 Dec 2004 20:22 GMT

Hello,

I have the following problem:

I have a TCP/IP server/client program(s) programmed with the
TcpListener/TcpClient class. The communication uses port 13000.

- It work fine from Windows2000(Client) to WindowsXP(Server)
- But it fails from Windows2000 to Linux(Server). It work from a Client
without .NET framework to the same server programm under Linux.

Has anybody an idea?

Thanks
Ralf

Reply to this Message

Mujtaba Syed - 20 Dec 2004 20:55 GMT

Ah, is this one of those little-endian vs. big-endian problems?
Try using a port like 9898 and see.

Mujtaba.

> Hello,
>
[quoted text clipped - 11 lines]
> Thanks
> Ralf

Reply to this Message

Ralf Haenel - 20 Dec 2004 21:13 GMT

Yes it one of those problems... sorry for that silly question ... painful

and many thanks for your help.

Regards Ralf

> Ah, is this one of those little-endian vs. big-endian problems?
> Try using a port like 9898 and see.
[quoted text clipped - 16 lines]
> > Thanks
> > Ralf

Reply to this Message

Michal Dabrowski - 23 Dec 2004 11:52 GMT

>> I have the following problem:
>>
[quoted text clipped - 9 lines]
> Ah, is this one of those little-endian vs. big-endian problems?
> Try using a port like 9898 and see.

I've just read your post and I am wondering what have the endianness to do
with this issue? I'm really curious because I've never supposed that this
can be a problem (at least at the stage of establishing connection). Also,
why 9898 is better than 13000?

Michal Dabrowski

Reply to this Message

System.Net.Socket and Linux Server

Free Magazines