Linux clients in AD, can't ping hostname
 

In the school where I work we have AD (2 domain, students and staff)
I have some Linux clients in both, running Fedora and Debian, same problem with all:
'puters gets IP allright (DHCP), can surf, can browse all shares in the domain (smb:// ) connect to printers etc.
2 computers show up in 'AD Users and Computers' -> computers with hostname (one in each domain), 2 doesn't. (Now only those 2 has actually joined the domain, but at least one showed up before that.)
What is a real problem, since I need to use ssh/vnc between them, is that I can't reach any Linux-client by hostname, only IP.
My Linux-boxes easily pings windows-clients by hostname, but no computer - Linux or Windows - can reach any Linux by name.
So some way I believe they are not properly registered in DNS? Unfortunately DNS is not under my control, AD is but we're using other DNS-servers.
But then, that should work automatically?

Just a thought, I don't believe it's possible to install Active Directory on a machine without installing DNS. What you may have access to is an Organization Unit MMC which would allow you to add machine accounts to a domain without having access to the other services offered by there server (DNS, DHCP, Terminal Services, et cetera).

I'm mostly certain there's no way for a linux machine to "join" a domain in the sense of pressing a button or running a command and having it authorize it's presence within active directory. The best solution that comes to mind is having the names added to the DNS server manually and that should solve the problem.

The whole thing is completely crazy!

To start with: Yes we have our own domain, not only on OU. But it is a subdomain "linneskolan.uppsala.se" where DNS is handled by servers on skolnet.uppsala.se. It works.

BUT!
My libranet-computer, named li-bib1 gets via DHCP 10.0.5.5
Tracert from domainserver says 10.0.5.5 is li-elev
Traceroute on libranet says 10.0.5.5 is li-b40-6
Ping from domainserver to li-elev -> unreachable (yes, it hasn't been on since yesterday)
New tracert from domainserver says 10.0.5.5 is li-bok
ping li-bok gives correct adress 10.0.1.145

The same thing happens on both domains??? What the h** is going on???:scratch:

And no computer has any trouble at all connecting to internet...