khanikar@gmail.com wrote:

> Hi,
> I don't know if its by design or a limitation with Suse Desktop 10.1,
> I discovered that Suse needs to be the same broadcast domain in order
> to connect to a Windows domain (Suse and the Windows domain connected

It doesn't

> to the same broadcast domain). Suse can not connect through a router
> to a domain controller located in a different network, in which case I

It does.

> have to use FQDN instead of NetBIOS name. It looks like Suse is not
> supporting FQDN for Windows Domain login.

It does.

If it does not work then you will have to check that DNS, routing
and firewall are working as expected.

--
http://www.mailtrap.org.uk/