Name: JohnCarrJr Date: August 10, 2007 at 11:15:10 Pacific Subject: How do I block Google Talk? OS: Windows2003 CPU/Ram: P4 Model/Manufacturer: various
Comment:
OK, here's my problem. I am trying to block the IM feature of Google. In GMail, you can 'reply in chat', and IM between people. You can also download googletalk.exe and run that IM. I have successfully blocked AIM, yahoo, MSN, and ICQ, but GTalk is kicking my butt!
I've done internet searches, and some suggestions were to block talk.google.com:443 and talk.google.com:5522. I use a web filter program called Sentian N2H2, and I blocked those web sites.
As a further step, I spoofed the DNS name pointing talk.google.com to 127.0.0.1. So, pinging that name resolves to the loopback adress.
None of that works......
I installed googletalk, and signed in sucessfully. When I run a netstat, I see this:
Let me also mention what I think the real problem is here.
I believe that GTalk has been rewritten since many of these blocking solutions on the net have been posted. One solution mentioned 4 IP addresses on 4 different ports you needed to block. Fine. We went into our internet router (cisco 1841) and blocked those IP's. We thought we had it working, becuase when I went to sign it, it looked like it was timing out. But after about 2 min, GTalk found a way to get in! Grrrr. a netstat command showed new google servers with DIFFERENT IP addresses.
So, the question is, is there a list of google servers out there?
Or better yet, is there a way to block *-in-*.google.com? Those wildcards don't seem to work, or I haven't found a way to do it. Maybe I'm overcomplicating it. Maybe there's a simple solution.
You might want to contact support services for Sentian N2H2, to find out if you're able to block "*-in-*.google.com", with wildcards.
Also, you should run a packet capture from your machine, to find out what is really going on here. Ethereal or Wireshark will do the packet sniff task.
The information on Computing.Net is the opinions of its users. Such
opinions may not be accurate and they are to be used at your own risk.
Computing.Net cannot verify the validity of the statements made on this site. Computing.Net and Computing.Net, LLC hereby disclaim all responsibility and liability for the content of Computing.Net and its accuracy.
PLEASE READ THE FULL DISCLAIMER AND LEGAL TERMS BY CLICKING HERE