VirtualBox

Opened 16 years ago

Closed 15 years ago

Last modified 14 years ago

#2405 closed defect (fixed)

NAT network on Adapter not working on Windows GUEST

Reported by: jwithana Owned by:
Component: network/NAT Version: VirtualBox 2.0.2
Keywords: NAT networking Cc:
Guest type: Windows Host type: Linux

Description

I opened a new ticket as a follow on to #2286 due to the confusion.

I Cannot access the internet from Guest after upgrading from VB 2.0.0 to 2.0.2. In the Win Guest, the network shows as connected but no sites can be accessed by IE or Firefox. Firefox on the Ubuntu host works fine.

I tried to downgrade back to 2.0.0 but this still does not fix the issue.

Can you PLEASE tell me any tests you would like me to run on the UBUNTU HOST or WINDOWS GUEST and post the output?

Attachments (2)

WinXP-2008-10-25-11-21-38.log (43.3 KB ) - added by jwithana 16 years ago.
Log file for NAT network not work on XP guest + Ubuntu Hardy host
WinXP-2008-10-25-17-24-52.log (50.1 KB ) - added by jwithana 16 years ago.
Log file after upgrading to 2.0.4, problem still happens (no network on Win XP Guest)

Download all attachments as: .zip

Change History (15)

comment:1 by jwithana, 16 years ago

also, shared folders DOES work so i wonder if the whole networking is inoperational or just part of it?

comment:2 by Frank Mehnert, 16 years ago

Shared folders and networking are two completely different subsystems. Please could you attach a VBox.log file of such a session?

comment:3 by jwithana, 16 years ago

sure. where do i find this file?

comment:4 by Frank Mehnert, 16 years ago

Please go to the VM selector window, select the VM, click on the 'Machine' menu and select 'Show log ...'.

by jwithana, 16 years ago

Log file for NAT network not work on XP guest + Ubuntu Hardy host

comment:5 by jwithana, 16 years ago

sorry for the delay in supplying the log file

comment:6 by jwithana, 16 years ago

UBUNTU HARDY HOST

$ ifconfig -a

eth0 Link encap:Ethernet HWaddr 00:1d:09:80:76:b0

inet addr:192.168.1.67 Bcast:192.168.1.255 Mask:255.255.255.0 inet6 addr: fe80::21d:9ff:fe80:76b0/64 Scope:Link UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1 RX packets:533683 errors:0 dropped:0 overruns:0 frame:0 TX packets:676690 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:100 RX bytes:134255370 (128.0 MB) TX bytes:250373197 (238.7 MB) Memory:fdfc0000-fdfe0000

lo 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:15326 errors:0 dropped:0 overruns:0 frame:0 TX packets:15326 errors:0 dropped:0 overruns:0 carrier:0 collisions:0 txqueuelen:0 RX bytes:2662276 (2.5 MB) TX bytes:2662276 (2.5 MB)

comment:7 by jwithana, 16 years ago

WIN XP GUEST

Microsoft Windows XP [Version 5.1.2600] (C) Copyright 1985-2001 Microsoft Corp.

C:\Documents and Settings\Janaka>ipconfig /all

Windows IP Configuration

Host Name . . . . . . . . . . . . : perp-win
Primary Dns Suffix . . . . . . . :
Node Type . . . . . . . . . . . . : Unknown
IP Routing Enabled. . . . . . . . : No
WINS Proxy Enabled. . . . . . . . : No
DNS Suffix Search List. . . . . . : local


Ethernet adapter Local Area Connection 3:


Connection-specific DNS Suffix . : local
Description . . . . . . . . . . . : AMD PCNET Family PCI Ethernet Adapter
Physical Address. . . . . . . . . : 08-00-27-2A-FA-95
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.0.2.15
Subnet Mask . . . . . . . . . . . : 255.255.255.0
Default Gateway . . . . . . . . . : 10.0.2.2
DHCP Server . . . . . . . . . . . : 10.0.2.2
DNS Servers . . . . . . . . . . . : 10.0.2.3
Lease Obtained. . . . . . . . . . : Saturday, October 25, 2008 3:07:52 PM
Lease Expires . . . . . . . . . . : Sunday, October 26, 2008 3:07:52 PM


C:\Documents and Settings\Janaka>

by jwithana, 16 years ago

Log file after upgrading to 2.0.4, problem still happens (no network on Win XP Guest)

comment:8 by Frank Mehnert, 16 years ago

Please have a look at your log file. There are the following lines:

NAT: passing domain name local
NAT: DNS address: 192.168.1.1
NAT: ignored DNS address: 68.237.161.12  

Is 192.168.1.1 a valid name server? Or should the other one used?

in reply to:  8 comment:9 by jwithana, 15 years ago

192.168.1.1 is the router so prob not a good name server.

how can i make it NOT ignore DNS address: 68.237.161.12 ?

Replying to frank:

Please have a look at your log file. There are the following lines:

NAT: passing domain name local
NAT: DNS address: 192.168.1.1
NAT: ignored DNS address: 68.237.161.12  

Is 192.168.1.1 a valid name server? Or should the other one used?

comment:10 by Frank Mehnert, 15 years ago

Currently VirtualBox supports exactly one DNS server which is read from /etc/resolv.conf so you have to make sure the correct IP address comes first.

comment:11 by jwithana, 15 years ago

many thanks, that worked. DNS could be configured for a different primary fromt the GUI

was wondering if you would support 2 DNS servers in VBox in the future? or if it could be submitted to the suggestion box?

comment:12 by Frank Mehnert, 15 years ago

Component: networknetwork/NAT

comment:13 by Frank Mehnert, 15 years ago

Resolution: fixed
Status: newclosed

Starting with version 2.2.0 VirtualBox passes multiple DNS servers to the guest. So your problem should be fixed. You also might want to have a look at section 9.14 (Enabling DNS proxy in NAT networking mode). Though enabling the DNS proxy is not required to get this work.

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use