Re: Reaching public NNTP servers through SBS 2003 Std.
- From: "Fanie Smith" <fanie@xxxxxxxxxxx>
- Date: Thu, 21 Apr 2005 08:03:35 GMT
Thankyou for the response Charles,
You have assumed right with regards to RRAS, in fact there are no thirdparty
software running on my installation of SBS2003.
I have two NIC's, one pointing to the internet throught an external DSL
router/firewall with it's own DHCP and IP, the other pointing to the local
network.
========================
The IP addresses used are:
...192.168.1.1 to 192.168.1.9 (255.255.255.0) for internet network
...192.168.2.1 to 192.168.2.245 (255.255.255.0) for local network
The two NIC's are set up as follows:
1. Local Network Adaptor. IP 192.168.2.1 (Static)
Mask 255.255.255.0
Gateway ... blank
Primary DNS 192.168.2.1
Secondary DNS ... blank
WINS 192.168.2.1
2. Internet network adaptor. IP 192.168.1.2 (assigned by router DHCP)
Primary DNS 192.168.2.1
Secondary DNS ... blank
WINS .... blank
3. Under the NAT/Basic Firewall settings both NNTP (119) and NNTP/SSL (563)
are enabled.
4. Under DNS,
the interface for DNS requests is set to 192.168.2.1 (Local Network
adaptor's address).
the forwarders are set to my ISP supplied Primary and Secondary IP
adresses.
============================
I have gone through the KB article and verified every setting, and
partaining for the primary and secondary DNS servers of the ISP, all else
checked out OK. I supplied the above info for reference. Maybe you'll see
what I missed.
I've re-ran the CEICW twice, again carefully verifying all the settings.
Status still unchanged.
1.When connected through SBS2003.
...can browse the internet fine.
...can connect to the local NNTP server fine
...can connect to msnews.microsoft.com fine
!!!...can NOT connect to ISP's NNTP server.
2. When bypassing SBS2003, i.e connecting workstation (Windows 2000 Pro SP4)
directly to external router/firewall and using it's DHCP service, everything
is normal.
I am now short of reformatting the hard drive and re-run the complete setup.
May something went wrong during the installation.
The only error reported during the initial setup was a service that was not
available (if my memory does not fail me, it was Exchange) right at the end
of the setup...It then suggested the setup should be continued after a
reboot. I aknowledged and the system apeared normal. All the actions in the
to do list when without problems and I decided at the time that re-renunning
the install was not neccessary.
The only manual alterations I did was starting the NNTP and POP3 services
which I would need.
Any other ideas before I re-install.
Thanks, Fanie.
.
- Follow-Ups:
- Re: Reaching public NNTP servers through SBS 2003 Std.
- From: "Charles Yang [MSFT]"
- Re: Reaching public NNTP servers through SBS 2003 Std.
- References:
- Reaching public NNTP servers through SBS 2003 Std.
- From: Fanie Smith
- RE: Reaching public NNTP servers through SBS 2003 Std.
- From: "Charles Yang [MSFT]"
- Reaching public NNTP servers through SBS 2003 Std.
- Prev by Date: Re: Self Cert for SSL
- Next by Date: RE: Server Down, Need Help
- Previous by thread: RE: Reaching public NNTP servers through SBS 2003 Std.
- Next by thread: Re: Reaching public NNTP servers through SBS 2003 Std.
- Index(es):
Relevant Pages
|
