Koozali.org: home of the SME Server

SME6, HTTP Proxy & Windows Product Activation Problems

stocky

SME6, HTTP Proxy & Windows Product Activation Problems
« on: February 05, 2004, 11:25:33 PM »
We are using SME and LOVE it. The only problem we are having is (we think)in regards to the HTTP proxy. We download a lot of stuff from the net over and over again (windows updates for numerous PC's) and love the proxy feature as it reducing our downloads MASSIVELY. The problem we get is that NONE of the microsoft product activations work. We can access ports 80 & 443 so that is not a problem and our server is set to server only mode with a single NIC.
Symantec product activation works interestingly enough....
Can anyone shed light on this issue. We are somehwat nebies to LINUX based systems so be gentle....

Offline Boris

  • *
  • 783
  • +0/-0
Re: SME6, HTTP Proxy & Windows Product Activation Proble
« Reply #1 on: February 05, 2004, 11:40:35 PM »
Quote from: "stocky"
We can access ports 80 & 443 so that is not a problem and our server is set to server only mode with a single NIC.

I assume then that you are using another device as your firewall/gateway, correct? Are you still using your server-only SME as your proxy server for caching?
It is not clear how your network structured. Can you give more details?
...

matsk

SME6, HTTP Proxy & Windows Product Activation Problems
« Reply #2 on: February 05, 2004, 11:41:35 PM »
Try the method to check if "MS activation" works.

Check 1 - Port 80
1. Open Internet Explorer.Type http://www.microsoft.com:80 in the Address bar, and then press ENTER.
2. Type http://www.microsoft.com:80 in the Address bar, and then press ENTER.

Check 2 - Port 443
1. Open Internet Explorer.Type https://www.microsoft.com:443 in the Address bar, and then press ENTER.
2. Type https://www.microsoft.com:443 in the Address bar, and then press ENTER.

Reference :
http://support.microsoft.com/default.aspx?scid=kb;EN-US;291983


/Mats

stocky

SME6, HTTP Proxy & Windows Product Activation Problems
« Reply #3 on: February 05, 2004, 11:52:20 PM »
We use an ISDN router as our gateway and always have. The router used to be the DHCP server but has now got a static IP and the SME6 box is the DHCP Server. We use the SME box for file server, and the proxy was a nice bonus! Never used to have this problem before with just the ISDN router and no SME6 box. Again the SME6 box is just plugged into a port on our switch and configured as server only. We have tried the port 80 & 443 tests as suggested by MS and they work fine

Henk

SME6, HTTP Proxy & Windows Product Activation Problems
« Reply #4 on: February 06, 2004, 08:21:54 AM »
I´m having the same problem with server/gateway SME 6.0.

The Microsoft Test doesn´t test https on port 80 and http over port 443. Guess one of those should be open.

Offline markleman

  • ***
  • 66
  • +0/-0
    • http://www.leman.net
SME6, HTTP Proxy & Windows Product Activation Problems
« Reply #5 on: February 10, 2004, 05:39:28 PM »
I too have found problems using windows and office product activation.

Setup :
SME server v6 in server and gateway mode.
PC with fresh install of XP SP1 + all M$ windows update fixes, Office 2003 + all M$ office update fixes.

Neither windows or office would activate over the internet. Tried with automatic proxy detection, manual proxy settings and proxy disabled in Internet explored (M$ product activation appears to fetch these settings)

I can connect to http://www.microsoft.com:80 and https://www.microsoft.com:443 which is the test M$ recommend.

Unplug PC from e-smith local network and plug in to spare port on ADSL router (which is where the sme external interface is also connected), windows and office activate fine.

All very odd because I have had no problems with this before using SME5.x and probably 6b3 (but I can’t be 100% sure of that) so either something has changed in SME6 or M$ have changed something in a recent  windows update fix that breaks this.

Offline jmartin

  • ***
  • 58
  • +0/-0
    • http://www.ci.wayne.mi.us
SME6, HTTP Proxy & Windows Product Activation Problems
« Reply #6 on: February 12, 2004, 05:55:19 PM »
I wonder if this is similar/related to the problem I posted

http://forums.contribs.org/index.php?topic=20722.0


-Jeff

hpe

SME6, HTTP Proxy & Windows Product Activation Problems
« Reply #7 on: February 14, 2004, 11:25:55 AM »
Suggest to continue discussion here :

http://forums.contribs.org/index.php?topic=20797.0

As far as I can see this is Microsoft related.

-Hervé

Offline smeghead

  • *
  • 563
  • +0/-0
SME6, HTTP Proxy & Windows Product Activation Problems
« Reply #8 on: May 06, 2004, 09:59:22 AM »
.. been doin some research on this via digging through the log files; in dnscache/current I find this:

2004-05-06 15:44:42.052555500 rr cf2ef5e6 3600 1 dns1.one.microsoft.com. cf2e8c64
2004-05-06 15:44:42.052562500 rr cf2ef5e6 3600 1 dns2.one.microsoft.com. cf2e8c65
2004-05-06 15:44:42.052566500 rr cf2ef5e6 3600 1 dns3.one.microsoft.com. cf2e7f96
2004-05-06 15:44:42.052585500 rr cf2ef5e6 3600 1 dns4.one.microsoft.com. cf2e7f97
2004-05-06 15:44:42.052589500 rr cf2ef5e6 3600 ns one.microsoft.com. dns1.one.microsoft.com.
2004-05-06 15:44:42.052593500 rr cf2ef5e6 3600 ns one.microsoft.com. dns2.one.microsoft.com.
2004-05-06 15:44:42.052598500 rr cf2ef5e6 3600 ns one.microsoft.com. dns3.one.microsoft.com.
2004-05-06 15:44:42.052647500 rr cf2ef5e6 3600 ns one.microsoft.com. dns4.one.microsoft.com.
2004-05-06 15:44:42.052652500 rr cf2ef5e6 3600 ns one.microsoft.com. dns5.one.microsoft.com.
2004-05-06 15:44:42.052657500 rr cf2ef5e6 3600 ns one.microsoft.com. dns7.one.microsoft.com.
2004-05-06 15:44:42.052661500 stats 25362 22593828 3 0
2004-05-06 15:44:42.052664500 cached 1 dns1.one.microsoft.com.
2004-05-06 15:44:42.052668500 cached 1 dns2.one.microsoft.com.
2004-05-06 15:44:42.052687500 cached 1 dns3.one.microsoft.com.
2004-05-06 15:44:42.052691500 cached 1 dns4.one.microsoft.com.
2004-05-06 15:44:42.052694500 tx 2 1 dns5.one.microsoft.com. . c0249411 c00505f1 c1000e81 c021040c 803f0235 c620400c 8009006b 80080a5a c6290004 c0cbe60a ca0c1b21 c0702404 c03a801e
2004-05-06 15:44:42.315128500 rr c0249411 172800 1 a.gtld-servers.net. c005061e
2004-05-06 15:44:42.315136500 rr c0249411 172800 1 b.gtld-servers.net. c0210e1e
2004-05-06 15:44:42.315140500 rr c0249411 172800 1 c.gtld-servers.net. c01a5c1e
2004-05-06 15:44:42.315144500 rr c0249411 172800 1 d.gtld-servers.net. c01f501e
2004-05-06 15:44:42.315162500 rr c0249411 172800 1 e.gtld-servers.net. c00c5e1e
2004-05-06 15:44:42.315166500 rr c0249411 172800 1 f.gtld-servers.net. c023331e
2004-05-06 15:44:42.315170500 rr c0249411 172800 1 g.gtld-servers.net. c02a5d1e
2004-05-06 15:44:42.315225500 rr c0249411 172800 1 h.gtld-servers.net. c036701e
2004-05-06 15:44:42.315229500 rr c0249411 172800 1 i.gtld-servers.net. c02bac1e
2004-05-06 15:44:42.315234500 rr c0249411 172800 1 j.gtld-servers.net. c0304f1e
2004-05-06 15:44:42.315238500 rr c0249411 172800 1 k.gtld-servers.net. c034b21e
2004-05-06 15:44:42.315242500 rr c0249411 172800 1 l.gtld-servers.net. c029a21e
2004-05-06 15:44:42.315246500 rr c0249411 172800 1 m.gtld-servers.net. c037531e
2004-05-06 15:44:42.315334500 rr c0249411 172800 ns com. f.gtld-servers.net.
2004-05-06 15:44:42.315338500 rr c0249411 172800 ns com. g.gtld-servers.net.
2004-05-06 15:44:42.315342500 rr c0249411 172800 ns com. h.gtld-servers.net.
2004-05-06 15:44:42.315346500 rr c0249411 172800 ns com. i.gtld-servers.net.
2004-05-06 15:44:42.315350500 rr c0249411 172800 ns com. j.gtld-servers.net.
2004-05-06 15:44:42.315354500 rr c0249411 172800 ns com. k.gtld-servers.net.
2004-05-06 15:44:42.315376500 rr c0249411 172800 ns com. l.gtld-servers.net.
2004-05-06 15:44:42.315380500 rr c0249411 172800 ns com. m.gtld-servers.net.
2004-05-06 15:44:42.315416500 rr c0249411 172800 ns com. a.gtld-servers.net.
2004-05-06 15:44:42.315420500 rr c0249411 172800 ns com. b.gtld-servers.net.
2004-05-06 15:44:42.315424500 rr c0249411 172800 ns com. c.gtld-servers.net.
2004-05-06 15:44:42.315428500 rr c0249411 172800 ns com. d.gtld-servers.net.
2004-05-06 15:44:42.315432500 rr c0249411 172800 ns com. e.gtld-servers.net.
2004-05-06 15:44:42.315435500 stats 25362 22594713 3 0
2004-05-06 15:44:42.315438500 cached 1 f.gtld-servers.net.
2004-05-06 15:44:42.315460500 cached 1 g.gtld-servers.net.
2004-05-06 15:44:42.315463500 cached 1 h.gtld-servers.net.
2004-05-06 15:44:42.315466500 cached 1 i.gtld-servers.net.
2004-05-06 15:44:42.315469500 cached 1 j.gtld-servers.net.
2004-05-06 15:44:42.315472500 cached 1 k.gtld-servers.net.
2004-05-06 15:44:42.315475500 cached 1 l.gtld-servers.net.
2004-05-06 15:44:42.315478500 cached 1 m.gtld-servers.net.
2004-05-06 15:44:42.315482500 cached 1 a.gtld-servers.net.
2004-05-06 15:44:42.315485500 cached 1 b.gtld-servers.net.
2004-05-06 15:44:42.315503500 cached 1 c.gtld-servers.net.
2004-05-06 15:44:42.315506500 cached 1 d.gtld-servers.net.
2004-05-06 15:44:42.315509500 cached 1 e.gtld-servers.net.
2004-05-06 15:44:42.315512500 tx 2 1 dns5.one.microsoft.com. com. c01a5c1e c036701e c0210e1e c029a21e c02bac1e c005061e c02a5d1e c00c5e1e c034b21e c0304f1e c037531e c01f501e c023331e
2004-05-06 15:44:42.331370500 rr c01a5c1e 172800 ns microsoft.com. dns1.cp.msft.net.
2004-05-06 15:44:42.331377500 rr c01a5c1e 172800 ns microsoft.com. dns1.dc.msft.net.
2004-05-06 15:44:42.331381500 rr c01a5c1e 172800 ns microsoft.com. dns1.sj.msft.net.
2004-05-06 15:44:42.331385500 rr c01a5c1e 172800 ns microsoft.com. dns1.tk.msft.net.
2004-05-06 15:44:42.331404500 rr c01a5c1e 172800 ns microsoft.com. dns3.uk.msft.net.
2004-05-06 15:44:42.331408500 stats 25362 22594840 3 0
2004-05-06 15:44:42.331411500 cached 1 dns1.cp.msft.net.
2004-05-06 15:44:42.331414500 cached 1 dns1.dc.msft.net.
2004-05-06 15:44:42.331459500 cached 1 dns1.sj.msft.net.
2004-05-06 15:44:42.331462500 cached 1 dns1.tk.msft.net.
2004-05-06 15:44:42.331465500 cached 1 dns3.uk.msft.net.
2004-05-06 15:44:42.331468500 tx 3 1 dns5.one.microsoft.com. microsoft.com. 4136f8de 4004191e cf2e8a14 d5c79097 cf2ef5e6
2004-05-06 15:44:42.432197500 rr c0702404 172800 1 a.gtld-servers.net. c005061e
2004-05-06 15:44:42.432205500 rr c0702404 172800 1 b.gtld-servers.net. c0210e1e
2004-05-06 15:44:42.432209500 rr c0702404 172800 1 c.gtld-servers.net. c01a5c1e
2004-05-06 15:44:42.432213500 rr c0702404 172800 1 d.gtld-servers.net. c01f501e
2004-05-06 15:44:42.432231500 rr c0702404 172800 1 e.gtld-servers.net. c00c5e1e
2004-05-06 15:44:42.432235500 rr c0702404 172800 1 f.gtld-servers.net. c023331e
2004-05-06 15:44:42.432238500 rr c0702404 172800 1 g.gtld-servers.net. c02a5d1e
2004-05-06 15:44:42.432290500 rr c0702404 172800 1 h.gtld-servers.net. c036701e
2004-05-06 15:44:42.432294500 rr c0702404 172800 1 i.gtld-servers.net. c02bac1e
2004-05-06 15:44:42.432298500 rr c0702404 172800 1 j.gtld-servers.net. c0304f1e
2004-05-06 15:44:42.432302500 rr c0702404 172800 1 k.gtld-servers.net. c034b21e
2004-05-06 15:44:42.432306500 rr c0702404 172800 1 l.gtld-servers.net. c029a21e
2004-05-06 15:44:42.432310500 rr c0702404 172800 1 m.gtld-servers.net. c037531e
2004-05-06 15:44:42.432330500 rr c0702404 172800 ns com. a.gtld-servers.net.
2004-05-06 15:44:42.432333500 rr c0702404 172800 ns com. g.gtld-servers.net.
2004-05-06 15:44:42.432337500 rr c0702404 172800 ns com. h.gtld-servers.net.
2004-05-06 15:44:42.432341500 rr c0702404 172800 ns com. c.gtld-servers.net.
2004-05-06 15:44:42.432345500 rr c0702404 172800 ns com. i.gtld-servers.net.
2004-05-06 15:44:42.432349500 rr c0702404 172800 ns com. b.gtld-servers.net.
2004-05-06 15:44:42.432438500 rr c0702404 172800 ns com. d.gtld-servers.net.
2004-05-06 15:44:42.432442500 rr c0702404 172800 ns com. l.gtld-servers.net.
2004-05-06 15:44:42.432482500 rr c0702404 172800 ns com. f.gtld-servers.net.
2004-05-06 15:44:42.432486500 rr c0702404 172800 ns com. j.gtld-servers.net.
2004-05-06 15:44:42.432490500 rr c0702404 172800 ns com. k.gtld-servers.net.
2004-05-06 15:44:42.432493500 rr c0702404 172800 ns com. e.gtld-servers.net.
2004-05-06 15:44:42.432497500 rr c0702404 172800 ns com. m.gtld-servers.net.
2004-05-06 15:44:42.432501500 stats 25362 22595725 3 0
2004-05-06 15:44:42.432504500 cached 1 a.gtld-servers.net.
2004-05-06 15:44:42.432526500 cached 1 g.gtld-servers.net.
2004-05-06 15:44:42.432529500 cached 1 h.gtld-servers.net.
2004-05-06 15:44:42.432532500 cached 1 c.gtld-servers.net.
2004-05-06 15:44:42.432535500 cached 1 i.gtld-servers.net.
2004-05-06 15:44:42.432538500 cached 1 b.gtld-servers.net.
2004-05-06 15:44:42.432541500 cached 1 d.gtld-servers.net.
2004-05-06 15:44:42.432544500 cached 1 l.gtld-servers.net.
2004-05-06 15:44:42.432547500 cached 1 f.gtld-servers.net.
2004-05-06 15:44:42.432551500 cached 1 j.gtld-servers.net.
2004-05-06 15:44:42.432569500 cached 1 k.gtld-servers.net.
2004-05-06 15:44:42.432572500 cached 1 e.gtld-servers.net.
2004-05-06 15:44:42.432575500 cached 1 m.gtld-servers.net.
2004-05-06 15:44:42.432578500 tx 3 1 dns5.one.microsoft.com. com. c023331e c029a21e c00c5e1e c02a5d1e c036701e c005061e c01f501e c02bac1e c0304f1e c037531e c034b21e c0210e1e c01a5c1e
2004-05-06 15:44:42.622519500 drop 25361 input/output error

(after this point the process cycles with the same result)

Now I have limited knowledge of the format and syntax of these lines of info but even I understand the word 'drop'.  Could someone with a better understanding of dnscache look into this and perhaps provide some more detail on what is actually happening & why?

HTH
..................