Take a client and ping 192.168.0.1 and even if it fails in command prompt
type this in:
arp -a
look for ARP entry for 192.168.0.1. If there is none present, check the
cabling (that cables are working and that they are switched in the right
port (leading to internal LAN not external network)...
Mike
**************
Here is an example of ARP entry for my gateway.
C:\>arp -a
Interface: 10.10.0.103 --- 0x10004
Internet Address Physical Address Type
10.10.0.1 00-80-c8-24-3c-65 dynamic
"Gary K. Brown" <(E-Mail Removed)> wrote in message
news:67d701c47580$ef09d840$(E-Mail Removed)...
> all cards have masks of 255.255.255.0 and 192.168.0.##
> IPs. Yes, just one gateway configured to my internet. I
> did point to the windows 2003 server (192.168.0.1) in the
> PCs nic tcp/ip DNS area.
>
> Gary
> >-----Original Message-----
> >Hi Gary,
> >
> >How is your internal network card configured? On
> internal network card check
> >IP and subnet mask definition. Check that your server
> has same subnet mask
> >as your clients do.
> >
> >You should also have only one default gateway configured
> on server itself.
> >Only network card leading to the internet (external NIC)
> should have default
> >gateway...
> >
> >I hope this helps,
> >
> >Mike
> >
> >"Gary K. Brown" <(E-Mail Removed)>
> wrote in message
> >news:683e01c4757d$922de6a0$(E-Mail Removed)...
> >> I am replacing NT with 2003 new install. I have a nic
> >> for my local network which has XP PCs and a nic for
> >> internet. I have installed 2003 and used the role for
> >> the first server process. I can get to the internet
> >> fine. I cannot ping any PCs on the local network.
> They
> >> can ping each other but cannot ping the server. all on
> >> 192.168.0.##. 2003 recognizes the 100mb network when I
> >> plug in the lan cable. I am stumped. What am I
> missing?
> >
> >
> >.
> >
|