Welcome to ISAserver.org
Forums |
Register |
Login |
My Profile |
Inbox |
RSS 
|
My Subscription |
My Forums |
Address Book |
Member List |
Search |
FAQ |
Ticket List |
Log Out
Starting to think this is a serious bug.... listeners
|
Users viewing this topic:
none
|
Logged in as: Guest
|
Login  | |
|
Starting to think this is a serious bug.... listeners - 22.Jul.2004 1:13:00 PM
|
|
|
penrose.l@2college.nl
Posts: 474
Joined: 29.Jan.2004
From: Netherlands
Status: offline
|
Hi ,
We use :
Microsoft ISA Server 2004
(c) 2004 Microsoft Corporation.
Version: 4.0.2161.50
With the following hardware :
Dell PowerEdge 1550
Intel Pro/1000 MT Quad port gb Server adapter.
---------
I install Windows 2003.
I configure it to use 4 networks
- 172.16.x.x / 192.168.x.x / 145.x.x.x /10.1.x.x
I install ISA 2004
I make a Server Publishing Rule :
- Publish POP3 to 172.16.4.253 listen on ALL NETWORKS.
ISA sets a listener on the External network ( 145.x.x.x ) and that's it.. it doesn't bind the others.
Now I tried removing the rule , changing it to ONLY bind external , works... changing it to ONLY bind internal ( any of em ) and it doesn't work.
Can anyone reproduce this ? It would help to know we're not the only ones coping with this error.
btw : This all worked in Beta 2 , it didn't work in RC1 but we hoped it would in final release , it doesn't.
I will try to install Beta 2 again ( sigh... ) to see if it works. I will keep you posted.
Kind regards,
Lex P.
The question is still : Anyone else experienced this ?
|
|
|
|
|
RE: Starting to think this is a serious bug.... listeners - 22.Jul.2004 1:28:00 PM
|
|
|
penrose.l@2college.nl
Posts: 474
Joined: 29.Jan.2004
From: Netherlands
Status: offline
|
Ok ,
I removed ISA 2004 Standard edition , and rebooted ( ofcourse ) and reinstalled the ISA 2004 BETA 2 version.
EVERYTHING WORKS LIKE A FRIGGIN CHARM !
aargh I'm getting crazy the beta works and the final doesn't...
omg help me I'm starting to throw all my monitors and keyboards out of the window here....
|
|
|
|
|
RE: Starting to think this is a serious bug.... listeners - 22.Jul.2004 1:56:00 PM
|
|
|
penrose.l@2college.nl
Posts: 474
Joined: 29.Jan.2004
From: Netherlands
Status: offline
|
Ok , I reinstalled ISA 2004 standard , did exactly the same as in Beta 2 , and it just doesn't work.
Beta 2 works / Standard final release doesn't work.
..............
|
|
|
|
|
RE: Starting to think this is a serious bug.... listeners - 22.Jul.2004 2:39:00 PM
|
|
|
penrose.l@2college.nl
Posts: 474
Joined: 29.Jan.2004
From: Netherlands
Status: offline
|
Ok I have some additional testing info :
The setup as I first tried doesn't work .
However , if I remove ALL networks , and only keep the default 'internal network' and 'external network' and I make internal = 172.16.x.x ( range of published server ) and connect using 192.168.x.x ( now on the EXTERNAL network ) it works !...
As soon as I make a new network ( I don't even change the rules or anything ) and put in the 192.168.x.x range ( internal / external / VPN / etc.. doesn't matter ) the binding fails and publishing doesn't work anymore.
So , I assume that in order to use publishing in ISA 2004 ( non beta coz there it worked ) you need to have :
- The published server MUST be in the default INTERNAL network
- The Client connecting to the published server MUST be in the External network ( in other words , if it's defined as anything else than nothing , it will fail to work )
... this is seriously frustrating...
|
|
|
|
|
RE: Starting to think this is a serious bug.... listeners - 22.Jul.2004 5:40:00 PM
|
|
|
tshinder
Posts: 47659
Joined: 10.Jan.2001
From: Texas
Status: offline
|
quote:
Originally posted by Lex Penrose:
Hi ,
We use :
Microsoft ISA Server 2004
(c) 2004 Microsoft Corporation.
Version: 4.0.2161.50
With the following hardware :
Dell PowerEdge 1550
Intel Pro/1000 MT Quad port gb Server adapter.
---------
I install Windows 2003.
I configure it to use 4 networks
- 172.16.x.x / 192.168.x.x / 145.x.x.x /10.1.x.x
I install ISA 2004
I make a Server Publishing Rule :
- Publish POP3 to 172.16.4.253 listen on ALL NETWORKS.
ISA sets a listener on the External network ( 145.x.x.x ) and that's it.. it doesn't bind the others.
Now I tried removing the rule , changing it to ONLY bind external , works... changing it to ONLY bind internal ( any of em ) and it doesn't work.
Can anyone reproduce this ? It would help to know we're not the only ones coping with this error.
btw : This all worked in Beta 2 , it didn't work in RC1 but we hoped it would in final release , it doesn't.
I will try to install Beta 2 again ( sigh... ) to see if it works. I will keep you posted.
Kind regards,
Lex P.
The question is still : Anyone else experienced this ?
Hi Lex,
That's a pretty unusual rule, to publish to all networks. I would tune the Publishing Rules with specific listeners and create serveral rules. All Networks is usually a bad way to go, unless you want to block something (and even then, I've seen unintended effects).
HTH,
Tom
|
|
|
|
|
RE: Starting to think this is a serious bug.... listeners - 22.Jul.2004 5:41:00 PM
|
|
|
tshinder
Posts: 47659
Joined: 10.Jan.2001
From: Texas
Status: offline
|
quote:
Originally posted by Lex Penrose:
Ok ,
I removed ISA 2004 Standard edition , and rebooted ( ofcourse ) and reinstalled the ISA 2004 BETA 2 version.
EVERYTHING WORKS LIKE A FRIGGIN CHARM !
aargh I'm getting crazy the beta works and the final doesn't...
omg help me I'm starting to throw all my monitors and keyboards out of the window here....
Hi Lex,
Yes, but beta 2 had a LOT of bugs. I don't think publishing with a listener for "Anywhere" is a good way to do for Server Publishing Rules (never occured to me to use this approach).
Thanks!
Tom
|
|
|
|
|
RE: Starting to think this is a serious bug.... listeners - 22.Jul.2004 5:46:00 PM
|
|
|
tshinder
Posts: 47659
Joined: 10.Jan.2001
From: Texas
Status: offline
|
Hi Cko,
This might help, but remember, this has nothing to do with Server Publishing:
to make DCC and IDENT for for mirc, add the following the the Firewall CLient Application Servers on the ISA server and then update the ISA Clients
[mirc32]
NameResolutionForLocalHost=P
ServerBindTcpPorts=113,1025-5000
[mirc]
NameResolutionForLocalHost=P
ServerBindTcpPorts=113,1025-5000
HTH,
Tom
|
|
|
|
|
RE: Starting to think this is a serious bug.... listeners - 23.Jul.2004 9:25:00 AM
|
|
|
penrose.l@2college.nl
Posts: 474
Joined: 29.Jan.2004
From: Netherlands
Status: offline
|
Hi Tom ,
We publish our servers both internally and externally , so the easiest was to publish on 'All networks'. In Beta this worked , but now you have to define NAT relation between networks.
Kind regards,
Lex P.
|
|
|
|
|
RE: Starting to think this is a serious bug.... listeners - 25.Jul.2004 5:12:00 PM
|
|
|
tshinder
Posts: 47659
Joined: 10.Jan.2001
From: Texas
Status: offline
|
Hi Lex,
OK, I guess I never considered that scenario.
Thanks!
Tom
|
|
|
|
 New Messages |
 No New Messages |
 Hot Topic w/ New Messages |
 Hot Topic w/o New Messages |
 Locked w/ New Messages |
 Locked w/o New Messages |
|
 Post New Thread
Reply to Message
Post New Poll
Submit Vote
Delete My Own Post
Delete My Own Thread
Rate Posts |
|
Printable Version
![[Smile]](/image/smiles/smile.gif)
