Server cannot ping itself by FQDN when BusinessHub wireless connection is enabled

[__Matthew]

Hi,

Probably a simple problem, but I have to concede I need help.

Im a mature final year comp. sci. student trying to set up a windows domain at home.

Steps to recreate the problem -----------------------------------------------------------------

- BT Business Hub (gateway.2wire.net)

- new Server2008 install, connects wirelessly to hub

- added Active Directory Services Role

- ran dcpromo.exe

- named new domain somename.com

- ping localhost:

      pinging win-machine.somename.com [127.0.0.1] from 127.0.0.1 with 32 bytes of data: 

      Reply from 127.0.0.1: time<1ms

      Reply from 127.0.0.1: time<1ms....

- ping somename.com

       pinging somename.com [192.168.1.65] from 192.168.1.65 with 32 bytes of data:

        general failure

        general failure....

- Also cannot launch Active Directory Users and Computers etc. without errors.

-----------------------------------------------------------------------------

Halfway Solutions ------------------------------------------------------------

- if I cut off the wireless connection ping win-machine.somename.com works fine.

- if i disable IPv4 in wireless adapter settings then ping -4 win-machine.somename.com works fine.

- similarly if IPv6 is disabled here, ping -6 win-machine.somename.com also works fine. 

-----------------------------------------------------------------------------

Notes --------------------------------------------------------------------------

- I have added 'win-machine.somename.com' to the hub's dns resolution table

- However, 'win-machine' is also a non-deletable DNS entry in the hub's dns table.

- ping fails with or without hub (192.168.1.254) as alternate dns server 

- ping fails with or without Wireless adapter connection-specific DNS suffix as somename.com

------------------------------------------------------------------------------------

I'm plumb out of ideas.

I suspect that the ping is getting thrown out by the hub's two DNS records (1: win-machine.gateway.2wire.net 2: win-machine.somename.com), but how to get the two to play nicely? 

[__Matthew]

OK, solved it,

It was the hubs firewall. I did try to turn the firewall off before, but hub told me it couldnt.

I now realize that DMZ mode is the only way to turn the firewall off!

Edit---------------------------------------

No joy, the problem persists.

DMZ just unleashes a world of pain.

Reverting to previous hub-as-gateway, server-gets-dhcp-address, setup.

Will post back if I find a solution.

----------------------------------------------

[mattspchelp · Accepted solution]

Just a simple noob idea

Your pinging the server wich is going to your router wich will resolve the somone.com to an IP on the web if its not registered to your server on the WWW

try pinging win-machine.somename.com this should return with data

[mattspchelp]

ha ha just thinking add somone.com to dns table with your Servers IP

unless youve done that

[__Matthew]

OK, by the title I should mark your answer as the solution, and believe me I am grateful, 

 I've renamed the domain to somename.lab.

ping now works using FQDN, 127.0.0.1, and 'localhost' from the server machine,

but there is still the same old issue...

Problem -------------------------------------------------------------------

- boot the server machine

- login

- opening IE works fine for now & I can access web nicely while server roles load

- ping 192.168.1.254 (hub):

       pinging 192.168.1.254 with 32 bytes of data:

       reply from 192.168.1.254 bytes:32 time:40ms TTL:50

       reply from 192.168.1.254 bytes:32 time:40ms TTL:50

- as soon as server roles finish loading, internet access disappears, all roles have red cross...

- ping 192.168.1.254 (hub):

       pinging 192.168.1.254 with 32 bytes of data:

       general failure

       general failure...

- ping 192.168.1.65:

       pinging 192.168.1.65 with 32 bytes of data:

       general failure

       general failure...

- disabling the wireless connection makes all server roles work fine.

-------------------------------------------------------------------------------------------------

I still suspect the router's gateway.2wire.net 'domain(?)' is the cause of the problem.

Basically, how can win-machine.somename.lab, either on a static ip in the hub's private network or in dmzplus:

----Use the hub for dhcp, gateway and alternate dns

----Use the server for dns & domain controller

Should the server domain be a subdomain of the hub's: eg: somename.lab renamed somename.gateway.2wire.net?

I will post back if I find a way that works.

[__Matthew]

OK, I had some other issues that were upsetting the setup.

- could have been caused by renaming the domain, broken ram, or some tinkering in the registry 

What I've done is a total format, reinstall & start from scratch.

but I've ditched the domain - for now - as it doesn't offer anything I can't get with less maintenance by other means.

maybe I'll retry later.