Re:Thanks for the replies
This is what I did to "solve" the situation:
Step1: I've setup my router to IP 192.168.0.5, on the same subnet mask as my network (255.255.255.0). I also disabled dhcp on the router.
Step2: On the Server side (which is 192.168.0.1 with AD,DNS,DHCP), on DHCP options for the scope, I had:
003 Router -> (none, since I had no gateway/router)
006 DNS -> 192.168.0.1 (So that every workstation who connects to the domain get's the domain DNS server plus it's added on the DNS for resolution. For example, a workstation named "posto01" will resolve to "posto01.myofficedomain.com" where myofficedomain.com is the domain name)
Then, I changed the settings to the following:
003 Router -> 192.168.0.5
006 DNS -> 192.168.0.5, 192.168.0.1 (on this order)
Now some more questions:
1) Before changing the settings, if I went to a workstation and ping "posto01.myofficedomain.com", it would resolve to the machine's IP (retrieved from DNS on the server), and ping it successfully. Now, after the changes, it no longer works … it only works if I ping "posto01.myoffice.com". Is there any special reason for this to happen?
2) I'm not really sure at this precise moment, but I do believe that if I change the order of the DNS option, for 192.168.0.1 first and 192.168.0.5 second, my access will stop working. That must have something to do will that "DNS forwarding" requirement … so as I see things, I would only put 192.168.0.1 as DNS server (the windows DNS), then I would setup the DNS on the server to forward failed lookups to 192.168.0.5 … it this correct? How to do it?
Re:you need to disable DHCP on the router (shouldn't have 2 servers, unless they are aware of each other and working together. Hard to do with a router and MS DHCP servers).
On the server, you need to add a router option to the scope to point to the router (I think you mentioned it's 192.168.0.5). You should also add the DNS server options while you are there. If you want an internal DNS server, but still want to resolve outside names, you need to setup forward lookups. This MAY require forwarding ports on the router (I'm not sure). The other option is to put the server as DNS 1 and then your ISP's DNS server as DNS2 in the options for the DHCP scope. Then the client will fall back to DNS2 for Inet lookups, and DNS1 (your server) for internal lookups.
Re:The original routers IP was 192.168.1.1. I changed it because my network is based on 192.168.0.??? with 255.255.255.0 as subnet mask.
So I had to change it to 192.168.0.5 (I choosed the 5), so the network clients could ping/access the machine. I'm right about this requirement, right?
Re:Some add … pinging the 194.65.100.117, which should be my ISP Primary DNS server, as it's said by my router's status page, results in nothing … cannot ping. Probably because of subnet mask?
Re:Hi,
I'm here again … here are some outputs from another workstation. In this case, this workstation and server are connected, and router dhcp is disabled.
ipconfig /all
Configura??o IP do Windows
Nome do sistema anfitri?o. . . . .: posto01
Sufixo DNS principal. . . . . . . : office.com
Tipo de nó. . . . . . . . . . . . : Desconhecido
Rota IP activado. . . . . . . . . : N?o
WINS Proxy activado . . . . . . . : N?o
Lista de procura de sufixo de DNS : office.com
Adaptador ethernet Liga??o de área local:
Sufixo DNS específico da liga??o. :
Descri??o . . . . . . . . . . . . : Realtek RTL8139 Family PCI Fast Ethernet NIC
Endere?o físico . . . . . . . . . : 0B-50-FA-C2-14-9D
DHCP activado . . . . . . . . . . : Sim
Autoconfigura??o activada . . . . : Sim
Endere?o IP . . . . . . . . . . . : 192.168.0.100
Máscara de sub-rede . . . . . . . : 255.255.255.0
Gateway predefinido . . . . . . . : 213.13.135.14 <-desperate attempt
192.168.0.5
Servidor DHCP . . . . . . . . . . : 192.168.0.1
Servidores DNS. . . . . . . . . . : 192.168.0.5 <-desperate attempt
192.168.0.1
Concess?o obtida. . . . . . . . . : quarta-feira, 30 de Mar?o de 2005 15:11:45
Concess?o obtida válida até . . . : quinta-feira, 7 de Abril de 2005 15:11:45
ping google.com
A enviar para google.com [216.239.37.99] com 32 bytes de dados:
O pedido excedeu o tempo.
O pedido excedeu o tempo.
O pedido excedeu o tempo.
O pedido excedeu o tempo.
Estat?sticas de ping para 216.239.37.99:
Pacotes: Enviados = 4, Recebidos = 0, Perdidos = 4 (perda: 100%),
ping 216.239.37.99
A enviar para 216.239.37.99 com 32 bytes de dados:
O pedido excedeu o tempo.
O pedido excedeu o tempo.
O pedido excedeu o tempo.
O pedido excedeu o tempo.
Estat?sticas de ping para 216.239.37.99:
Pacotes: Enviados = 4, Recebidos = 0, Perdidos = 4 (perda: 100%),
In a desperate attempt to make this work, I've added a gateway and dns setting on the dhcp options, which were passed to the workstation (are indicated in bold on ipconfig).
Any help much appreciated and needed … I'm looking at a non-working internet sharing … and it's very very important I set this to work today.
Thanks …
Re:Originally posted by: guy
Sounds like it might be DNS without taking a longer look. Can you ping google.com by IP but not by name? 216.239.57.99
Another piece of advice. Don't post your public IP address on a message board. That's an invitation though anand's board is typically an ethical group. It's still a bad idea generally.
Lol, I've made a quick "clean" of any personal data, still it seems I missed a bit Thanks
I'll try ping on google.com. What should I look for after that?
My DNS server (windows) is giving DNS server 192.168.0.1 (himself, the server). Do I need to add another IP? If I ping 194.65.100.117 on working config, it cannot reach it … that IP is supposed to be the Primary DNS Server given on the status page of the router, most probably my ISP one.
Re:Sounds like it might be DNS without taking a longer look. Can you ping google.com by IP but not by name? 216.239.57.99
Another piece of advice. Don't post your public IP address on a message board. That's an invitation though anand's board is typically an ethical group. It's still a bad idea generally.
0 Comments.