locked
Can't connect to router! RRS feed

  • Question

  • I have recently built a server and installed WHS 2003 on it. I am having difficulty getting the router set to accept the connection. Sorry I am just new at servers and require some direction here.

    The relevant information is as follows: Dlink Router  DSL-2640B PPPoE in Bridge mode (I also run a Voip ATA), set to Obtain  Gateway Automatically, NAT, Firewall & Wan enabled.

    Router IP 192.168.1.1, Subnet 255.255.255.0, Enabled DHCP Server Start IP 192.168.1.2 End 192.168.1.254.

    So here is what's happening. I can ping the Server from the client PC, put not vice/versa (Server IP addy 127.0.0.1)

    Looks like I have set the 4 PCs, 1 ATA, 1 Wii & printer behind the ADSL router firewall.

    Info from the server remote access configuration page are as follows: Router IP Address - not found, Home Server Physical Address = not found.

    I have tried to use the port forwarding but could use some direction here.

     Any info would be greatly appreciated. Thx

     

    Monday, July 25, 2011 2:50 PM

Answers

  • If you haven't installed any network drivers on your server, that's almost certainly the source of your problem. The address you say you're pinging for your server, 127.0.0.1, is absolutely not your server if you're using the ping command from a client; it's the local loopback address, which means that it's your client responding to itself. Having illuminated LEDs on your server's NIC only indicates that it's connected physically to your network, not that it has obtained a network connection. And so on.

    Please install the correct 32 bit network drivers for Windows Server 2003 on your server if available, or for XP if you can't locate Windows Server 2003 drivers.


    I'm not on the WHS team, I just post a lot. :)
    Tuesday, July 26, 2011 3:25 AM
    Moderator

All replies

  • It's not completely clear to me how your network is configured, I'm afraid.

    The supported configuration is to have the server and all client computers on the same subnet, behind the same router, etc. So your connections will look something like this:

    Internet -> Broadband modem -> router -> all network devices including your server.

    Anything that changes this (such as using a VPN connection, or putting your server in your router's DMZ) can interfere with the proper functioning of your server.

    I note that you say your server is reporting an IP address of 127.0.0.1. This is the local loopback address, not the IP address your server's network interface card has obtained. Could you run "ipconfig /all" on your server and post the results?


    I'm not on the WHS team, I just post a lot. :)
    Monday, July 25, 2011 5:50 PM
    Moderator
  • Thanks for your speedy reply and yes you are correct in the way I would like to configure the network. Internet -> ADSL combination modem/router -> all network devices including server.

    From the server I can't use the ipconfig /all cmd, get an error of Windows IP Configuration. This is somewhat odd. I looked at the Bios, the ethernet connection is active & the LED is working, but updates did not run. I don't believe I have to install a NIC as this is a newer ASUS board.

    Any further thoughts??

    Monday, July 25, 2011 8:40 PM
  • I don't think your se4rver is actually connected to your network, though the error you report is sort of vague. :) Make sure you have the right drivers installed: Windows Server 2003 32 bit by preference, or XP 32 bit if those aren't available.

    Also, try a different port for your server on your router (or switch). These devices do go bad eventually. If your router supports segmenting a network based on connection type (usually putting all wireless on one network segment, and all wired connections on another) see if you can disable this functionality and get everything onto a single network segment.


    I'm not on the WHS team, I just post a lot. :)
    Monday, July 25, 2011 9:06 PM
    Moderator
  • I believe it's not connecting to the router either, did not run updates etc. I know the cables good, router lights etc. Do I need to place Internet Connection setting in Server? I don't believe so since the server should connect through the router network.

    What additional info can you give for port setting? I tried under  Nat Virtual Server this: Server Name: server,  Port 443 TCP Server IP Address 192.168.1.250 and the same for Port 4125 with no luck.


    Additionally I can ping 127.0.1.0 & 127.0.0.1 the server ok.
    Monday, July 25, 2011 10:39 PM
  • Have you installed any network drivers on your server?
    I'm not on the WHS team, I just post a lot. :)
    Tuesday, July 26, 2011 2:13 AM
    Moderator
  • I was only able to install the WHS. Here is additional info from the PC (client ) that my ADSL is connected.

    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\User>cd\

    C:\>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : User-PC
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection 2:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ether
    net Controller
       Physical Address. . . . . . . . . : 00-23-54-38-0A-1D
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigab
    it Ethernet Controller
       Physical Address. . . . . . . . . : 00-23-54-38-08-8E
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::357d:5115:a41d:e0d4%10(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.6(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Monday, July 25, 2011 10:24:27 PM
       Lease Expires . . . . . . . . . . : Tuesday, July 26, 2011 10:24:27 PM
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 6:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{5D569E15-1DF2-46B4-BCAC-75715F794
    996}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 7:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{9AA69CF6-8383-42D8-B07A-F563E828B
    853}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 02-00-54-55-4E-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:2cfc:1be7:3f57:fef9(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::2cfc:1be7:3f57:fef9%12(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    C:\>

    Hope this provides additional info for help, Thx.

    Tuesday, July 26, 2011 2:41 AM
  • JUst installed the WHS on the server, I have the following info from the PC (client) connected to my ADSL router.

    Microsoft Windows [Version 6.0.6001]
    Copyright (c) 2006 Microsoft Corporation.  All rights reserved.

    C:\Users\User>cd\

    C:\>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : User-PC
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection 2:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ether
    net Controller
       Physical Address. . . . . . . . . : 00-23-54-38-0A-1D
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigab
    it Ethernet Controller
       Physical Address. . . . . . . . . : 00-23-54-38-08-8E
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::357d:5115:a41d:e0d4%10(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.6(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Monday, July 25, 2011 10:24:27 PM
       Lease Expires . . . . . . . . . . : Tuesday, July 26, 2011 10:24:27 PM
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tunnel adapter Local Area Connection* 6:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{5D569E15-1DF2-46B4-BCAC-75715F794
    996}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 7:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : isatap.{9AA69CF6-8383-42D8-B07A-F563E828B
    853}
       Physical Address. . . . . . . . . : 00-00-00-00-00-00-00-E0
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes

    Tunnel adapter Local Area Connection* 11:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Teredo Tunneling Pseudo-Interface
       Physical Address. . . . . . . . . : 02-00-54-55-4E-01
       DHCP Enabled. . . . . . . . . . . : No
       Autoconfiguration Enabled . . . . : Yes
       IPv6 Address. . . . . . . . . . . : 2001:0:4137:9e76:2cfc:1be7:3f57:fef9(Pref
    erred)
       Link-local IPv6 Address . . . . . : fe80::2cfc:1be7:3f57:fef9%12(Preferred)
       Default Gateway . . . . . . . . . : ::
       NetBIOS over Tcpip. . . . . . . . : Disabled

    C:\>

    Tuesday, July 26, 2011 3:03 AM
  • Only installed the WHS on the server. Here is the info from the PC (client) that is connected to the ADSL router/modem.

    C:\>ipconfig /all

    Windows IP Configuration

       Host Name . . . . . . . . . . . . : User-PC
       Primary Dns Suffix  . . . . . . . :
       Node Type . . . . . . . . . . . . : Hybrid
       IP Routing Enabled. . . . . . . . : No
       WINS Proxy Enabled. . . . . . . . : No

    Ethernet adapter Local Area Connection 2:

       Media State . . . . . . . . . . . : Media disconnected
       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Marvell Yukon 88E8056 PCI-E Gigabit Ether
    net Controller
       Physical Address. . . . . . . . . : 00-23-54-38-0A-1D
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes

    Ethernet adapter Local Area Connection:

       Connection-specific DNS Suffix  . :
       Description . . . . . . . . . . . : Marvell Yukon 88E8001/8003/8010 PCI Gigab
    it Ethernet Controller
       Physical Address. . . . . . . . . : 00-23-54-38-08-8E
       DHCP Enabled. . . . . . . . . . . : Yes
       Autoconfiguration Enabled . . . . : Yes
       Link-local IPv6 Address . . . . . : fe80::357d:5115:a41d:e0d4%10(Preferred)
       IPv4 Address. . . . . . . . . . . : 192.168.1.6(Preferred)
       Subnet Mask . . . . . . . . . . . : 255.255.255.0
       Lease Obtained. . . . . . . . . . : Monday, July 25, 2011 10:24:27 PM
       Lease Expires . . . . . . . . . . : Tuesday, July 26, 2011 10:24:27 PM
       Default Gateway . . . . . . . . . : 192.168.1.1
       DHCP Server . . . . . . . . . . . : 192.168.1.1
       DNS Servers . . . . . . . . . . . : 192.168.1.1
       NetBIOS over Tcpip. . . . . . . . : Enabled

    Tuesday, July 26, 2011 3:11 AM
  • If you haven't installed any network drivers on your server, that's almost certainly the source of your problem. The address you say you're pinging for your server, 127.0.0.1, is absolutely not your server if you're using the ping command from a client; it's the local loopback address, which means that it's your client responding to itself. Having illuminated LEDs on your server's NIC only indicates that it's connected physically to your network, not that it has obtained a network connection. And so on.

    Please install the correct 32 bit network drivers for Windows Server 2003 on your server if available, or for XP if you can't locate Windows Server 2003 drivers.


    I'm not on the WHS team, I just post a lot. :)
    Tuesday, July 26, 2011 3:25 AM
    Moderator
  • Only installed the WHS on the server that's all. Here is some info from the PC ( client ) that is connected via cat5 to the ADSL router/modem when I used ipconfig /all.

    Node type: Hybrid

    IP routing Enabled: No

    WINS Proxy Enabled: No

     

    Ethernet Adapter Local Area Connection 2:

    Media State: Disconnected

    DNS Suffix: Marvell etc....

    Phys. Add: etc., etc.

    DHCP: enabled: Yes

    Autoconfig Enabled: Yes

     

    Ethernet adapter Local Area Connection:

    DNS Suffix: Marvell Yukon etc.  (Note this is a different physical addy than the one above)

    DHCP enabled: Yes

    Autoconfig Enabled: Yes

    IPv4 Add: 192.168.1.6(Preferred)

    Subnet mask: 255.255.255.0

    Lease Exp: 1 day

    Default Gateway: 192.168.1.1

    DHCP Server: 192.168.1.1

    DNS Server:192.168.1.1

    NetBios over Tcpip: Enabled

     

    I checked the Connection 2 in network & sharing, it's not connected (this board has 2 Ethernet ports)

    Should the DHCP on the adapter be disabled, I seem to recall reading something about a possible conflict if both router & Ethernet adapter DHCP are enabled???

    Tuesday, July 26, 2011 3:37 AM
  • You aren't listening to me. Your problem is with your server, not your client. Information from your client isn't helpful at this point, since all it says is that your client is properly configured.

    Please confirm the installation of the correct network drivers for your server. Not your client.


    I'm not on the WHS team, I just post a lot. :)
    Tuesday, July 26, 2011 3:44 AM
    Moderator
  • Sorry for the multiple sends above, did not look like the copy/paste was work due to big delays.

    In any event, yes I agree with you, yes this looks like a server issue, where do I look for the drivers, eg. folder, which drivers are you referring to and how would they be installed, no connection to network??


    I beleive you are referring to the server MB  (Asus)  Bios driver, correct? I see they have XP Drivers of a different variety. I will try a few & see what happens here.
    Tuesday, July 26, 2011 4:01 AM
  • Assuming your Server NIC is not working due to lack of drivers, your only option is to log in to your server directly, which will mean connecting a keyboard/monitor etc. You can then check if the NIC is working by looking in Device Manager or executing an ipconfig/all in a command window on your server to see if it's getting a valid IP address (if you are using DHCP). If not working, use a client PC to locate the correct drivers on the Internet (Server 2003 or failing that XP 32 bit) and copy to a USB stick. On the server, through device manager update drivers for the NIC and point to the location on your USB stick.

     


    Phil P.S. If you find my comment helpful or if it answers your question, please mark it as such.
    Tuesday, July 26, 2011 11:20 AM
  • Good morning Ken,

    Thanks for sending me in the right direction yesterday. I went to the MB site & downloaded the XP bios & LAN drivers, flashed them to the server. Now I can connect. Sometimes issues can arise when new board meets old OS & old operator.

    Thx again, now it's on to connecting the clients to the server, wish me luck.

     

     

    Tuesday, July 26, 2011 3:10 PM
  • If you haven't installed any network drivers on your server, that's almost certainly the source of your problem. The address you say you're pinging for your server, 127.0.0.1, is absolutely not your server if you're using the ping command from a client; it's the local loopback address, which means that it's your client responding to itself. Having illuminated LEDs on your server's NIC only indicates that it's connected physically to your network, not that it has obtained a network connection. And so on.

    Please install the correct 32 bit network drivers for Windows Server 2003 on your server if available, or for XP if you can't locate Windows Server 2003 drivers.


    I'm not on the WHS team, I just post a lot. :)

    THANKS SO MUCH.  IT'S TAKEN ME AAAAGES TO FIND THIS.  Problem solved, mucho gracias dude, may you have a long and prosperous life.

    Eoin

    Saturday, July 7, 2012 4:03 PM