Simon James
asked on
cannot ping router (192.168.1.254)
hi...
I have server core 2019 (core 2016 is ok to. all the commands i have tried from server core 2016, work on 2019). This is a test box away from the production servers.
all firewalls are down for the purposes of this test. i have ad ds running/installed
test-dnsserver comes back as success, but the round trip takes about 10-11 seconds.
ping. allowed icmp and everything pings accept the router (192.168.1.254)
get-netconnectionprofile. changed it from public to private networkcategory. Shouldn't this be domain authentication?.
nslookup. default server unknown, address ::1. Is this to do ipv6 not being found in dns?. the name for this is "network". should this be different, say, to domain name instead of network?
lets get the ping for the router out of the way first.
That's enough questions for now, thank you for any help you can offer, Simon
I have server core 2019 (core 2016 is ok to. all the commands i have tried from server core 2016, work on 2019). This is a test box away from the production servers.
all firewalls are down for the purposes of this test. i have ad ds running/installed
test-dnsserver comes back as success, but the round trip takes about 10-11 seconds.
ping. allowed icmp and everything pings accept the router (192.168.1.254)
get-netconnectionprofile. changed it from public to private networkcategory. Shouldn't this be domain authentication?.
nslookup. default server unknown, address ::1. Is this to do ipv6 not being found in dns?. the name for this is "network". should this be different, say, to domain name instead of network?
lets get the ping for the router out of the way first.
That's enough questions for now, thank you for any help you can offer, Simon
::1 is localhost for IPv6..., if you have enabled IPv6 but didn;t provide any information in DNS that may cause timeouts looking for names withh addresses and vise versa.
ASKER
Hello, and thanks for your reply...!
The host I am run a ping on is the server core itself. All other clients (win 7, 10 etc) can ping the gateway address. All
other clients have internet access (noted, server core doesn't have internet access).
Its only a small network, say, 11 users. Do I really need ipv6 or can i disable it?. What would be the correct procedure
to do this?.
Guys there is no rush on this. Because its a test box feel free to try anything new you would like to try out
thank you..., Simon
The host I am run a ping on is the server core itself. All other clients (win 7, 10 etc) can ping the gateway address. All
other clients have internet access (noted, server core doesn't have internet access).
Its only a small network, say, 11 users. Do I really need ipv6 or can i disable it?. What would be the correct procedure
to do this?.
Guys there is no rush on this. Because its a test box feel free to try anything new you would like to try out
thank you..., Simon
You only need IPv6 if you need IPv6 connectivity..., then again if you want/need IPv6 then start with the network first.
ROuters on IPv6, and get IPv6 rolled out..., then you can start thinking about IPv6 onservers.
ROuters on IPv6, and get IPv6 rolled out..., then you can start thinking about IPv6 onservers.
Once again... What is the IP address of the host you are pinging from?
ASKER
Sorry for that..., ip address ping from is 192.168.1.17, domain: rapidcomputers.co.uk, host: core-2019.
I don't need ipv6......
Thank you, simon
I don't need ipv6......
Thank you, simon
The only things that I can think of which would prevent one host from successfully pinging a router on the same network is
1) Wrong (incompatible) mask on the host or router.
2) An ACL (Access Control List) on the router denying the traffic (in this case, ping requests from an address).
3) An ACL on the switch denying the traffic.
1) Wrong (incompatible) mask on the host or router.
2) An ACL (Access Control List) on the router denying the traffic (in this case, ping requests from an address).
3) An ACL on the switch denying the traffic.
ASKER
Thanks for your input. I will hammer a few bt forums to see if they know any thing, thanks again, simon
This question needs an answer!
Become an EE member today
7 DAY FREE TRIALMembers can start a 7-Day Free trial then enjoy unlimited access to the platform.
View membership options
or
Learn why we charge membership fees
We get it - no one likes a content blocker. Take one extra minute and find out why we block content.
Can other hosts on that network ping the 192.168.1.254 address successfully?