Ubuntu Networking :: Windows Clients Lose Ability To Resolve Local Domain Names
Dec 2, 2010
I have an internal domain (dev.lan) for which my Ubuntu server is authoritative. We have a number of subdomains under that domain (test.dev.lan, svn.dev.lan, etc.). The server also acts as the primary DNS server for my office. It was originally set up under Ubuntu 8 and worked great.
However, ever since we upgraded to Ubuntu 10, our Windows clients periodically lose the ability to resolve domains on the dev.lan domain. Internal IP addresses can still be pinged from the Windows machines so it does not appear to be a network-connectivity issue. External domain names continue to resolve without any problems. The only workaround is to restart networking on the Windows clients. It's frustrating because it happens several times a day.
I recently installed bind9 on mandriva 2008.1, after having done the necessary configuration.. I still can't find my domain I configured cant ping on other machines on the LAN but can actually ping on any other website on the internet even though name server is configured to point to local machine..... I dont understand what I'm doing wrong.
I'll apologize in advance for I'm sure this has been covered already, but I'm not sure of the search terms to even use to begin solving this problem. I don't know what I don't know.
I have three computers on my home network and want to reach them by their name instead of IP address since their ip is dynamically assigned. I'm using a Linksys WRT54GL router and have noticed that there exists a "DHCP Clients Table" in the router that seems to hold all the necessary information - host names and ip addresses.
How can I get my computers to use that as the lookup table to resolve the host names? And is this even an optimal way of being able to resolve local names?
I want to use single label host names on my local LAN, without using any domain (at least no registered one). My machines should be named in a fashion similar to 'myserver', 'mydesktop' etc. so that i from a browser on any LAN machine may write 'http://myserver', and get the webserver on 'myserver' (so NO domain part, e.g. myserver.domain).
Do i need to create a DNS zone for each host or is there a way to put all host in a single zone, if so; which? Would such a name be considered a root domain?
I'm new here, so please be gentle! I recently installed F12 64 KDE on my Acer Aspire 1810TZ, could connect to the WLAN router but neither the native Konquerer nor Firefox could open any pages...
resolve.conf has the DNS according to DHCP offer, from command line dig properly resolves the name, ping (e.g. google) works, telnet to domain-name on port 80 works, GET too. When using the browser with the domain-name I tells me "Server not found", tcpdump doesn't display any activity. But when I manually change the domain-name with the IP (received by command line dig) then the browser has no problem how do browsers interact with the network resources of the OS?
I have three Debian systems running, along with several XP laptops, PS3 and two DirecTV systems. I use two of the three Debian systems as media servers, and the third is an older system mostly for playing around with. My home network is running fine with the following nuisance. The two newer Debian (Lenny) systems are <barney> and <mitzi>, the older is named <oscar>, running Debian Sarge 3.1. From either locally or remote login to <barney> and <mitzi> I can ssh into either of the other two systems, however when logged into <oscar> I cannot ssh by name to either of the other systems. e.g. ssh: mitzi: Temporary failure in name resolution..However, from <oscar> I can ping outside my network (e.g. ping www.google.com) with no problems.I can also ssh to the other systems via IP address, just not by name.
I've compared the /etc/ssh/ssh_config, /etc/resolv.conf, /etc/ssh/sshd_config and other files between the two systems and not seeing anything peculiar. arp, route, etc., don't show different behavior between the systems either.
dammit... all that typing and I hit the wrong "submit" button. *sigh*
Ok, I have a couple of SMTP servers for our infrastructure. They are running Postfix. I have them configured so that specific email addresses such as email@example.com and firstname.lastname@example.org all go to a new support server that I am building with osTicket. Lets call that server SUPP1.
SUPP1 runs sendmail from the default install of CentOS 5 i386. At this point everything runs great. New emails get added into the osTicket system via a pipe in sendmail. Here's where the problem comes in. In order to accept mail, sendmail has to have the domain listed in local-host-names and the addresses in virtusertable. That works just dandy. But in doing so, sendmail believes it is the destination SMTP server for "mydomain.com". That means that I can't send mail from that server back into my normal SMTP servers. So things like the LogWatch, cron jobs, etc can't send notifications. Is there a way to work around that? For sendmail to ignore local-host-names for outbound email or something?
We've been running samba on linux for a while and everything was fine. All of a sudden when you add new clients to the domain you get the error message :Logon Failure:unknown user name or bad password. This to me seems like a windows error message and not a samba error. When you remove an existing machine (ie on domain) and then try to rejoin it to the domain you fail.
I have a mac and an openSUSE box connected wirelessly to a router. From my mac, if I ping the Linux machine by both ip address and hostname "elmo.local", I get a response. If I ping my mac from the Linux machine using its ip address, I get a response. However, if I ping the mac from the Linux box using its name "kermit.local" - nothing!
This means in order to share files between them via the network, I have to use the ip address rather than name, but I'd rather not. When I had Ubuntu installed instead of openSUSE this all worked fine out of the box, so I'm assuming it's a problem with the setup of openSUSE rather than the router or the mac.
I configured my dns server running on redhat5(test.com, ip-192.168.10.1), all is working perfect on the server its-self and on the client machine(xp), it cant resolve the name [url] but can resolve when i use [url]are ok, nslookup displays the following error:
The reverse is working fine from the redhat machine, NO firewall on the client xp machine xp as host name is added in /etc/hosts
After upgrading my ubuntu server from 9.04 to 10.04, the window computers couldn't resolve samba shared names anymore, the error code displayed by Windows was 0x80070035.
I was using the ubuntu server as a samba server, using 'share' as the security authentication method, it has been working very well under previous ubuntu versions but, after upgrading to 10.04, the windows computers can't access the server shares anymore; the linux computers don't have any problems (I can access the shares from linux).
As a workaround, I've added the name of the server in c:windowssystem32driversetchosts; but I'd like to know how to fix the problem without modifying every windows computer.
I feel ashamed for even asking this, since it seems like there's about 3 samba questions here every day. However after an hour of searching, I keep finding strange variants that aren't what I need.
My Goal: Create a single file share on an Ubuntu Server - share it via samba to Windows clients that are on a domain with active directory. It sure would be nice if AD authentication would work - so users don't have to type in a linux user/passsword each time they want to access the share.
In my adventures, I've found the following items (which may overlap)
1. Joining the server to a Windows Domain
2. Turning the server into a Windows Domain Controller
3. Authentication with LDAP (still not quite sure how/what this would do)
4. Stuff with Kerberos
5. Lots of people bickering about Samba 3/4 & how it's impossible to make Samba a PDC.
I'm not sure if I need to make the ubuntu server a domain controller or not...all I want to do is create a file share and share it on the domain...I don't need to make the ubuntu server a domain controller for that, right? Maybe just a member? Maybe nothing at all?
I guess if I want to authenticate stuff correctly (or forward authentication requests? Not sure), I probably need to join the ubuntu server to the domain...I think.
But let's say I do join it to the domain...then how to I create a file share that is authenticated via active directory rather than a local ubuntu server account? I see a dozen guides on joining the server to the domain, but nobody ever mentions sharing the folder over the domain.
The lines are also blurred between joining Ubuntu to the domain and making it a domain controller. What should I keep an eye out to avoid in these tutorials?
I get lost between the Kerberos/LDAP/Samba/WinBind etc...and I have a feeling I don't need all of these for something this simple.
A while ago I downloaded a VMWare VM for 7.10. I then upgraded it to 8.10 and it was working just fine. I just did the upgrade to 10.04 and I'm having problems with my networking. The really odd thing is that I can ping machines on my local network and out on the Internet by IP address but it will not resolve names using DNS.
I've got the network set up for DHCP. I also tried DHCP address only and manually entered my DNS server addresses but still no luck on resolving names with DNS. At the end of the day, I don't really care if I get this fixed or just get a new VMWare VM. (I can't create one because I only have the player.)
i need to configure Redhat Linux as Domain Controller in my organisation, whee all of my clients PC's will be Windows XP or Windows 7 ( where i can login through Domain users ). what exactly i need to configure in Redhat Linux, i heard Configuring Samba as PDC is quite enough ? is that right ? then what is Open LDAP ? should i need to Configure Open LDAP also ?
I have a NAS server running Debian with Dnsmasq (local DNS and DHCP service). This is working well, including fetching upstream requests from my ISP's DNS service and caching them locally. I have another PC not running Ubuntu which happily resolves DNS and non-DNS names. E.g. Code: ping hagrid. ping hagrid both work.
However, this is not the case on my Ubuntu PC. It is only able to resolve DNS names, not non-DNS names. Code: ping hagrid. works but Code: ping hagrid does not. I have the standard nsswitch.conf and host.conf.
I have set up DNS server set up on my RH 5.5 system. It is working perfectly as Caching only Server but but when i tried to make it a primary server for a zone it didn't resolved. I am actually a newbie so please correct me if i am wrong somewhere. Here are my configuration files code...
I have setup an static IP on this server, it will ping internal sites , but when I try to browse the internet it does not do anything. I have set up the gateway, the firewall, and the domain fie, but still no luck.NOTE: When I try DHCP it will work ( it will resolve the DNS of the pages), but since this is a server it requires an static IP.
Is it possible to have one static IP address with a NAT network forwarding each domain name to certain internal/DMZ IP addresses? I know you can do it by port but if both websites are on port 80 can you forward to the corresponding server on the dmz.I ask this because I noticed the website braemere.com.au had to be typed into a web browser and entering the IP which is 22.214.171.124 did not take me to the website.
I have a windows PC and a fedora 13 linux box. When connecting to the linux from windows, I'd like to type the hostname instead of the ip address. Apart from setting the hostname, what do I have to do to publish my hostname on the intranet. (set up a nameserver?)
Though hostname works on the linux box, even this fails: nslookup myhostname Also I'm a newbie. I've tried installing some packages like samba and dhcp, using yum...;service chkconfig... and then checking whether nslookup or nmblookup work with my hostname. But it's just guesswork. Under system -> Administration there is no network option. but it is not clear what package is needed to install it, or whether such a thing is supported in fedora 13. I did try system-config-network, but it has few options none of which pertain to hostname resolution. The fedora manuals dont seem to cover it, at least in recognizable plainspeak to me.
I'm confused. Why do I get a response from ping for any scrambled internet server name I type in??The only thing that is necessary is to start with "vvvvvv."(It should be triple W in this post, but I need to do this work around due to the forum rules )And it always resolved to different IPs with similar ping times.What's going on?
Code: > ping vvvvvv.q3g87uv8123907.qt1 PING vvvvvv.q3g87uv8123907.qt1 (126.96.36.199) 56(84) bytes of data. 64 bytes from vvvvvv.q3g87uv8123907.qt1 (188.8.131.52): icmp_seq=1 ttl=249 time=55.6 ms
I used Likewise (specifically, likewise-open-gui) to add my computer to the Windows domain at work. I can log into the computer with my domain credentials.
Until I reboot.
If the computer ever shuts down fully, I get an authentication failure when I log in using the domain account. But if I log in using a local account and run likewise-open-gui again from there, everything works. I don't have to rejoin the domain, only launch the program, close it, and log out of the local account. This seems to allow me to log into the domain afterward.
Is there something in specific that I can add to my startup scripts that will connect me to the domain before login?
i have registered two domain names that i want to use to connect to my ubuntu server. I was wondering how to do this i was looking at bind9 but that didn't work that great. The server is behind a router with firewall i can connect to it using the external IP address but i like to use the two domain names if that is possible.
I have an Edubuntu server with two nics joined to the primary windows domain and I can log on with domain credentials and everything is AOK. I used LikewiseOpen 6 to join the server to the primary domain. So, on my Edubuntu server eth1 is connected to the primary domain and has a static IP. eth2 also has a static IP and is the DHCP for the thin client subnet, connected to a switch. IP forwarding is enabled.
So far, so good: I can log on the thin clients with one of the local accounts specified on the Edubuntu server and with that account I can surf the net and, if I supply domain credentials, browse the primary domain. Problem I have is:
I can't work out how to log on to the primary domain with a Active Directory account directly from a thin client. If I try DOMAINuser to log on, after giving the password, the password screen refreshes and 'domainuser@11.*.21.*'s password' appears under the blank password box. The IP in that message is the IP for the subnet and not the primary domain. I feel like I'm miss-understanding some basic simple step but I just can't figure it out.
I'm having really weird and frustrating DNS issues with my clients unable to properly resolve the server's ip address. They can resolve each other's, and outside systems, but not the server - at least, not correctly, and not all the time.
I have one Ubuntu server set up that does both DHCP and DNS serving to the Windows systems. The server has DNS forwarding turned on to forward to OpenDNS's servers (I've tried using my ISP's dns servers but the problem remains). The server is *not* set up as a firewall; I am actually using a DLink router for that, and the Dlink is *not* set up to serve up DHCP nor DNS.
What I am getting is that my clients - and there are nothing but Windows clients - will not resolve the name of the server. For example, if I do: ping linuxserver
I get back a false IP address of 192.168.0.64 (and I've seen once a 192.168.2.49).
If, however, I put a dot in there: ping linuxserver.
I get back the *correct* IP address of 192.168.0.2, and thereafter, ping'ng linuxserver without the dot will work. Until the dns cache expires, either naturally or with ipconfig /flushdns on the windows clients.
The client *are* getting valid dhcp leases and can resolve everything happy-happy, they just will not get the proper address of the server 100% of the time.