Re: 2003 server NetDiag results

One thing that is strange is your administrative distances are 20. Only one
NIC this server?

"andy smart" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
news:d99bib$l5d$1@xxxxxxxxxxxxxxxxxxxxxx
> Neteng wrote:
> > Can you post an 'ipconfig /all' and 'route print' ?
> >
> > "andy smart" <anonymous@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote in message
> > news:d98jik$147$1@xxxxxxxxxxxxxxxxxxxxxx
> >
> >>Hi
> >>
> >>We're installing a 2003 server for use with Exchange, and having run
> >>NetDiag we see some failures which puzzle us.
> >>
> >>Extracts from the netdiag.log file:
> >>_____________________________________________________________________
> >>Per interface results (with network specific information edited):
> >>
> >> Adapter : Local Area Connection
> >>
> >> Netcard queries test . . . : Passed
> >>
> >> Host Name. . . . . . . . . : correct server name
> >> IP Address . . . . . . . . : correct ip present
> >> Subnet Mask. . . . . . . . : correct ip present
> >> Default Gateway. . . . . . : correct ip present
> >> Dns Servers. . . . . . . . : correct ip present
> >>
> >>
> >> AutoConfiguration results. . . . . . : Passed
> >>
> >> Default gateway test . . . : Failed
> >> No gateway reachable for this adapter.
> >>
> >> NetBT name test. . . . . . : Passed
> >> [WARNING] At least one of the <00> 'WorkStation Service', <03>
> >>'Messenger Service', <20> 'WINS' names is missing.
> >>
> >> WINS service test. . . . . : Skipped
> >> There are no WINS servers configured for this interface.
> >>
> >>...
> >>
> >>Default gateway test . . . . . . . : Failed
> >>
> >> [FATAL] NO GATEWAYS ARE REACHABLE.
> >> You have no connectivity to other network segments.
> >> If you configured the IP protocol manually then
> >> you need to add at least one valid gateway.
> >>
> >
> >
____________________________________________________________________________
> >
> >>However as you can see the default gateway is present. We must be
> >>connecting to the gateway router specified as default gateway as we can
> >>connect to the internet from this server. Beyond the router there is a
> >>lot of NAT taking place due to the way in which our school broadband
> >>connection works, however there is no issue reaching the gateway IP
> >>specified.
> >>
> >>What could be the cause of this? I don't like just ignoring things
> >>without understanding what I am ignoring!
> >>
> >>andi
> >
> >
> >
> As requested - 'real' school information removed and replaced :-)
>
>
> ipconfig /all:
> Windows IP Configuration
> Host Name . . . . . . . . . . . . : taipan
> Primary Dns Suffix . . . . . . . : lizard.balamory.cbbies.sch.uk
> Node Type . . . . . . . . . . . . : Unknown
> IP Routing Enabled. . . . . . . . : No
> WINS Proxy Enabled. . . . . . . . : No
> DNS Suffix Search List. . . . . . : lizard.balamory.cbbies.sch.uk
> balamory.cbbies.sch.uk
> cbbies.sch.uk
> sch.uk
>
> Ethernet adapter Local Area Connection:
> Connection-specific DNS Suffix . :
> Description . . . . . . . . . . . : Intel(R) PRO/100+ Dual Port
> Server Adapter #2
> Physical Address. . . . . . . . . : 00-90-27-0C-41-5D
> DHCP Enbled. . . . . . . . . . . : No
> IP Address. . . . . . . . . . . . : 10.42.192.26
> Subnet Mask . . . . . . . . . . . : 255.255.252.0
> Default Gateway . . . . . . . . . : 10.42.192.1
> DNS Servers . . . . . . . . . . . : 10.42.192.18
>
> route print
>
> > IPv4 Route Table
> >
===========================================================================
> > Interface List
> > 0x1 ........................... MS TCP Loopback interface
> > 0x10004 ...00 90 27 0c 41 5d ...... Intel(R) PRO/100+ Dual Port Server
Adapter #2
> > ========================================================================
===
> >
===========================================================================
> > Active Routes:
> > Network Destination Netmask Gateway Interface
Metric
> > 0.0.0.0 0.0.0.0 10.42.192.1 10.42.192.26
20
> > 10.42.192.0 255.255.252.0 10.42.192.26 10.42.192.26
20
> > 10.42.192.26 255.255.255.255 127.0.0.1 127.0.0.1
20
> > 10.255.255.255 255.255.255.255 10.42.192.26 10.42.192.26
20
> > 127.0.0.0 255.0.0.0 127.0.0.1 127.0.0.1
1
> > 224.0.0.0 240.0.0.0 10.42.192.26 10.42.192.26
20
> > 255.255.255.255 255.255.255.255 10.42.192.26 10.42.192.26
1
> > Default Gateway: 10.42.192.1
> >
===========================================================================
> > Persistent Routes:
> > None
>
> tia
> andy


.

Relevant Pages

  • Re: VPN and remote gateway
    ... > It seems you use the wrong route add command. ... > when the VPN connection is established. ... > | using the remote network as my gateway. ...
    (microsoft.public.windows.server.sbs)
  • Re: problems opening AD Users & Computers
    ... the decision to make our main DC as a gateway to the internet. ... Connection specific DNS Suffix: ... Description:IntelPro/1000 MT Network Connection ... There is a 2nd DC in our organisation and that server will open up ...
    (microsoft.public.windows.server.active_directory)
  • Re: Dual NICs on Server 2003 issue
    ... as the primary and only DNS server as the 192.168.87.50 is the DNS server ... Do I have to add a route for that too? ... gateway you need to use static routing. ... connects via another gateway to a remote site that is on a 10.0.1.x ...
    (microsoft.public.windows.server.networking)
  • Re: 1 NIC Windows 2003 Domain; 1 Wireless NIC to Internet - Cant get both working
    ... >and also needs to use a Wireless NIC to connect to the Internet ... Each connection can specify a default gateway, ... and ittue the command 'route print' when both are ...
    (microsoft.public.windowsxp.network_web)
  • Re: 1 NIC Windows 2003 Domain; 1 Wireless NIC to Internet - Cant get both working
    ... >and also needs to use a Wireless NIC to connect to the Internet ... Each connection can specify a default gateway, ... and ittue the command 'route print' when both are ...
    (microsoft.public.windows.server.sbs)
Loading