Author Topic: Open DNS and office network  (Read 860 times)

Offline Georgetoon

  • Hero Member
  • *****
  • Posts: 3231
  • Don't rush the bacon.:)
    • Georgetoon Cartoons!
Open DNS and office network
« on: June 14, 2011, 12:19:26 PM »
I was having a problem having everything work on my PCLinuxOS notebook when connecting the internet.  The browser worked and I was able to hit the other machines on the network.  email, Weather Widgets, RadioTray did not connect to the internet.

I changed to Open DNS settings and everything for the internet now works.  Browser, Email, Weather Widgets, RadioTray, etc.  Everything connects to the internet.

However, I can no longer connect to other local machines on the office network 
Toonfully,

Mark
-----------
Lenovo 14" ThinkPad Edge (0578F5U) with Core i3 Processor(i3-370M) 2.40 GHz 4GB RAM
Acer Aspire 9300 Laptop
Desktop Icy Dock system with AMD PHENOM X4 QUADCORE 9650 2.3GHZ 4MB L1 , ‎NVidia GEFORCE 9400GT 1GB 2X DVI PCIE graphics card, 22" Chimei monitor.

Offline pags

  • Hero Member
  • *****
  • Posts: 2606
  • Keep it clean.
Re: Open DNS and office network
« Reply #1 on: June 15, 2011, 06:22:28 AM »
I was having a problem having everything work on my PCLinuxOS notebook when connecting the internet.  The browser worked and I was able to hit the other machines on the network.  email, Weather Widgets, RadioTray did not connect to the internet.

I changed to Open DNS settings and everything for the internet now works.  Browser, Email, Weather Widgets, RadioTray, etc.  Everything connects to the internet.

However, I can no longer connect to other local machines on the office network 

Your office's DNS was providing the name resolution for internal machines (which cannot be provide by an external DNS such as OpenDNS, because they are not aware of the office PCs, and I doubt your office wants them to be, or that they even have public IPs).
The office DNS may also use a transparent proxy (maybe even caching , for performance), which could include limited access to some ports, which could affect apps such as email, etc...; or block specific sites.

If you have a good relationship with the IT person in your office, they may be able to help you (or, you may be cautious, if you think they may feel slighted at your attempts to circumvent their security measures...)

If you know the IPs of the PCs you connect to, you could use those.  If they're static, you could even add them to you /etc/hosts file, and use that for name resolution.  If they're DHCP, and actually change, over time, then you'll be chasing a moving target...