proxmox will not let me connect!

  • Thread starter 40tonsofbananas
  • Start date
4

40tonsofbananas

Guest
So I'm trying to setup my quadcore 955 black edition running on a M4A79T Deluxe SE board with the built in ethernet, however the latest version of proxmox won't allow me to connect to it after installing to a terabyte hard disk.




I've run IFCONFIG and this is what the screen displays:


Link encap: Ethernet HWaddr 00:24:8c:6e:bd:c0
inet6 addr fe80:224:8cff:fe6e:bdc0/64 Scope: Link
UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric:1
RX Packets: 0 errors: 0 dropped: 0 overruns: 0 frame:0
TX packets: 68 errors: 0 dropped: 0 overruns: 0 carrier:0
collisions: 0 txqueueclcn: 1000
RX bytes: 0 (0.0
cool.png
TX bytes: 3328 (3.2KiB)

Link encap: Local Loopback
inet addr:127.0.0.1 Mask: 255.0.0.0
inet6 addr: ::1/128 Scope:Host
UP LOOPBACK RUNNING MTU:16436 Metric:1
RX packets: 40 errors:0 dropped: 0 overruns:0 frame:0
TX packets: 40 errors: 0 dropped:0 overruns:0 carrier:0
collisions: 0 txquelen:0
RX Bytes: 3864 (3.7 KiB) TX bytes: 3864 (3.7 KiB)

Link encap: UNSPEC HWAddr 00-00-00-00-00-00-00-00-00-00-00-00-00-00-00-00
inet6 addr: fe80::1/28 Scope:Link
UP BROADCAST POINTOPOINT RUNNING NOARP MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:0 errors:0 dropped:3 overruns:0 carrier:0
collisions:0 txquelen:0
RX bytes:0 (0.0B) TX bytes:0 (0.0B)

Link encap: Ethernet HWaddr:00:24:8c:6e:bd:c0
inetaddr:192.168.1.5 Bcast:192.168.1.255 Mask: 255.255.255.0
inet6 addr: fe80::224:8cff:fe6e:bdc0/64 Scope:Link
UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1
RX packets:0 errors:0 dropped:0 overruns:0 frame:0
TX packets:60 errors:0 dropped:0 overruns:0 carrier:0
collisions:0 txquelen:0
RX bytes(0.0B) TX Bytes:2776(2.7KiB)



My primary router is set up in this configuration:


Default Gateway: 96.253.86.1 DNS Server: 71.252.0.12
68.238.112.12
Although I have set the gateway and DNS server during installation to 192.168.1.1 for both, and the IP address as 192.168.1.5


Do I need to reinstall and use the default gateway as shown in my router? by the way, this is a cruddy MI424WR router. YUCK!


This is also as stated, hooked up directly to ethernet and appears to have a link.


I try to connect to 192.168.1.5 and it actually trys to connect for about a minute and then displays the typical "The connection has timed out" page.

The server at 192.168.1.5:)8006)is taking too long to respond.


If it matters, I am also logged in as root while trying to connect.
 
Your router gateway and DNS servers are different than a machine on your LAN uses. Since you have a router, you have to use the ROUTERS internal IP address (192.168.1.1) in order for it to work as a gateway. That has NOTHING to do with not being able to access the machine on the local LAN.

can you ping the IP of the server from command line on your machine?

What do you mean you are logged in as root while trying to connect?
 
pirateghost said:
Your router gateway and DNS servers are different than a machine on your LAN uses. Since you have a router, you have to use the ROUTERS internal IP address (192.168.1.1) in order for it to work as a gateway. That has NOTHING to do with not being able to access the machine on the local LAN.

can you ping the IP of the server from command line on your machine?

What do you mean you are logged in as root while trying to connect?
Click to expand...


Says 192.168.1.5 is unavailable.

The DNS servers are directly from the router.

I've logged into the server as root and tried to connect via a webbrowser however it doesn't allow me to connect as it's not even showing up on the router under the router's web interface.
 
If you set a static IP address on it, you wouldnt see it show up in the DHCP leases on the router. I still dont understand when you say you logged into the server as root and try to connect via a webbrowser. being logged in on the server has nothing to do with seeing the IP address on your network. I understand your DNS servers are direct from the router, but the routers configuration to get to the internet is not the same as your internal network configuration. the server needs a gateway (the internal ip of your router) in order to be able to get OUT of your network. It needs a name server in order to resolve DNS queries. neither of these things are related to being able to ping the server on your LAN.
 
I have TeamViewer if you would like to further query my network
 
pirateghost said:
If you set a static IP address on it, you wouldnt see it show up in the DHCP leases on the router. I still dont understand when you say you logged into the server as root and try to connect via a webbrowser. being logged in on the server has nothing to do with seeing the IP address on your network. I understand your DNS servers are direct from the router, but the routers configuration to get to the internet is not the same as your internal network configuration. the server needs a gateway (the internal ip of your router) in order to be able to get OUT of your network. It needs a name server in order to resolve DNS queries. neither of these things are related to being able to ping the server on your LAN.
Click to expand...


When I set up the configuration, I set the gateway and DNS server as 192.168.1.1 (the primary IP of the router)
 
40tonsofbananas said:
When I set up the configuration, I set the gateway and DNS server as 192.168.1.1 (the primary IP of the router)
Click to expand...
And that is what you should have done.

from the command line on the server, can you ping 192.168.1.1?
then can you ping 8.8.8.8?
also try to ping the client you are attempting to connect from
 
40tonsofbananas said:
So I'm trying to setup my quadcore 955 black edition running on a M4A79T Deluxe SE board with the built in ethernet, however the latest version of proxmox won't allow me to connect to it after installing to a terabyte hard disk.
...
Link encap: Ethernet HWaddr 00:24:8c:6e:bd:c0
inet6 addr fe80:224:8cff:fe6e:bdc0/64 Scope: Link
UP BROADCAST RUNNING MULTICAST MTU: 1500 Metric:1
RX Packets: 0 errors: 0 dropped: 0 overruns: 0 frame:0
TX packets: 68 errors: 0 dropped: 0 overruns: 0 carrier:0
collisions: 0 txqueueclcn: 1000
RX bytes: 0 (0.0 TX bytes: 3328 (3.2KiB)
...
Click to expand...

Hi,
you receive nothing on this device - this can't be right. Something wrong with the NIC (driver)/ Cable or Switch-Port.

What is the output of following commands?
Code: 
ifconfig -a
lspci -vs `lspci | grep -i ether | awk '{print $1}'`
Udo
 
Re-formatted using this information:

Country; United States
Time zone: America/New_York
Keyboard Layout: U.S. English

password: **********
confirm: **********
e-mail *****@****************


Hostname: proxmox.local
IP Address: 192.168.1.23
Netmask: 255.255.255.0
Gateway: 192.168.1.1
DNS Server: 192.168.1.1
 
Last edited by a moderator:
I still cannot connect to the web interface after re-formatting. What can I do to fix this?

I can however ping 192.168.1.23
 
You must log in or register to reply here.

About

The Proxmox community has been around for many years and offers help and support for Proxmox VE, Proxmox Backup Server, and Proxmox Mail Gateway.
We think our community is one of the best thanks to people like you!

Quick Navigation

Home Get Subscription Wiki Downloads Proxmox Customer Portal About

Get your subscription!

The Proxmox team works very hard to make sure you are running the best software and getting stable updates and security enhancements, as well as quick enterprise support. Tens of thousands of happy customers have a Proxmox subscription. Get yours easily in our online shop.

Buy now!
Community platform by XenForo® © 2010-2024 XenForo Ltd.
Top Bottom
Back