|
Home > Archive > 70-216 > August 2003 > Qod 8/29 - Wins
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
|
|
| blackwidow 2003-08-28, 7:49 pm |
| You do ipconfig /all on your win2k pro machine and this is what you see:
Name: Cool2kPro
IP : 192.168.1.40
Mask: 255.255.255.224
gateway: 192.168.1.33
WINS: 192.168.0.100
The WINS server's name is OURWINS1
You then do this ping:
C:> ping salespro1
Reply from salespro1 [192.168.0.105]
4 successful replies.
You then do this ping:
C> ping OURWINS1
Unknown host OURWINS1 (basically unsuccessful in pinging)
Why can't you ping OURWINS1?
(No multichoice. Put on your troubleshooting hats people and have a go at it)
 | |
| karlisi 2003-08-29, 2:05 am |
| Hmmm... Its about name resolution. There is no DNS server defined for 'Cool2kPro', instead we have WINS server defined. Its on different subnet and this subnet is reachable because we can ping 'salespro1' from this subnet, so GW and routing is OK and WINS server works.
Because our target too is on different subnet (we can see it on ipconfig output) broadcasting will not help to resolve IP address, the only choice is WINS. We need also target host name registered on WINS server.
It seems like WINS server knows nothing about himself and my guess is -
on 'OURWINS1' there is no WINS servers defined. On WINS server this record must point to itself. | |
| blackwidow 2003-08-29, 2:15 am |
| Applause for Karlisi
You got it exactly right. OURWINS1 does not have an IP in it's own configuration for a WINS server. Hence everybody else (hopefully) is registering themselves in the WINS database, except for the WINS ITSELF!
Hence, we can ping salespro1 because WINS resolved that name, but when we pinged the WINS server's own name, it did'nt exist in the wins database.
Cool huh? | |
| karlisi 2003-08-29, 2:20 am |
| Cool
BTW what the time now, I think its about midnight (it is 9:20 AM on my clock) |
|
|
|
|