Posts Tagged With ‘Windows&8217


Microsoft Always Sucks

I got this message while trying to install Windows 2003 Server to Dell Inspiron 1520


iPhone Killer

iPhone killer …


When Bogazici Guys Suck

When you need to access remote windows share over network, you just mount the share to your local linux folder like you do when mounting local disks.

mount -t cifs //10.187.12.107/e -o username=merturk /media/remote/ –verbose

This command should ask the password of the user then mounts the remote win share to your local. However, if you cannot see what you are supposed to see in your local mount point, simply inspect the kernel message using dmesg. If you see an output like what I saw today

CIFS VFS: Error connecting to IPv4 socket. Aborting operation
CIFS VFS: cifs_mount failed w/return code = -512

then you should start to think if all windows I.T. managers sucks or just windows guys who are graduated from Bogazici.

In Brief, this log message tells you, you have a network issue, probably you are banned to access windows shares in some subnetworks of your network like me ….


How Microsoft restricts developers on networking

Nowadays I’m interested in raw network programming which gives you ability to construct you building custom headers and makes sure that OS kernel does not modify these headers. I’ve started a VS.NET C++ console application (unmanaged) and typed several lines to test.

#include “stdafx.h”
#include

int _tmain(int argc, _TCHAR* argv[])
{
SOCKET s;
int optval = 1;

s = socket(AF_INET, SOCK_RAW, IPPROTO_RAW);
setsockopt(s, IPPROTO_IP, IP_HDRINCL, (char *)&optval, sizeof optval);

return 0;
}

I got an error message;

Error 1 error C2065: ‘IP_HDRINCL’ : undeclared identifier ..

After some quick research I’ve come up to this solution. If you are interested in low level networking like me, you should have Unix based boxes instead of Microsoft. The reason is simple; restrictions. Raw socket programming is available in all Unix, and Linux OSs on the other hand MS based OSs is restricted to NT based ones. None of Windows 95, 98, 98SE supported raw sockets. It becames available on Windows from Windows 2000, Windows XP but with Windows XP SP2 this feature is disabled. Quick summary from Microsoft’s specification for this issue:

The Windows implementation of TCP/IP still supports receiving traffic on raw IP sockets. However, the ability to send traffic over raw sockets has been restricted in two ways:

* TCP data cannot be sent over raw sockets.
*UDP datagrams with invalid source addresses cannot be sent over raw sockets. The IP source address for any outgoing UDP datagram must exist on a network interface or the datagram is dropped.

Microsoft encourages the developers to use their products but restricts them to full access. There is a conflict but this is Microsoft. They are doing their best !!!


Setting up a cluster

It took 2 days to read and learn and setup a JEE based cluster for different types of platforms. I still have some problems in linux running Fedora Core 7. Problem is setting up connection on node instances. A good start for JEE cluster can be found here.