G
Guest
Hi,
When I ran NetDiag on my workstation, I got a couple of NetDiag errors.
First, brief info on the network: This is a brand new W2K3 network I'm
setting up. So far I have the following in the network:
DC1 - Domain Controller, AD integrated DNS, DHCP and WINS
DC2 - Domain Controller, AD integrated DNS
GateKeeper - Member server running ISA 2004 w/ internal, external and DMZ
zones
NAV - Member server running Symantec NAV Enterprise
MSX - Member server
SamWS - My XP Pro SP2 workstation
The first error I'm getting is w/ Default Gateway. I entered the internal IP
of GateKeeper under Server Options for WINS. The error reads "[FATAL] No
gateways are reachable.
Second error I'm getting is [FATAL] Kerberos does not have a ticket for
host/SamWS.MyDomain.Local
First question: What am I supposed to enter for Gateway server option for
WINS server? I thought entering the internal IP of the firewall server would
be right thing. Any idea what might be causing this error?
Second question: Don't know how to even attack the kerberos problem
I ran NetDiag because I had a bunch of errors on my servers. I'd appreciate
some pointers on how to resolve these issues.
When I ran NetDiag on my workstation, I got a couple of NetDiag errors.
First, brief info on the network: This is a brand new W2K3 network I'm
setting up. So far I have the following in the network:
DC1 - Domain Controller, AD integrated DNS, DHCP and WINS
DC2 - Domain Controller, AD integrated DNS
GateKeeper - Member server running ISA 2004 w/ internal, external and DMZ
zones
NAV - Member server running Symantec NAV Enterprise
MSX - Member server
SamWS - My XP Pro SP2 workstation
The first error I'm getting is w/ Default Gateway. I entered the internal IP
of GateKeeper under Server Options for WINS. The error reads "[FATAL] No
gateways are reachable.
Second error I'm getting is [FATAL] Kerberos does not have a ticket for
host/SamWS.MyDomain.Local
First question: What am I supposed to enter for Gateway server option for
WINS server? I thought entering the internal IP of the firewall server would
be right thing. Any idea what might be causing this error?
Second question: Don't know how to even attack the kerberos problem
I ran NetDiag because I had a bunch of errors on my servers. I'd appreciate
some pointers on how to resolve these issues.