VirtualBox

Opened 7 years ago

Closed 7 years ago

Last modified 7 years ago

#16944 closed defect (invalid)

Can not connect to Oracle 12c in the guest - Virtualbox 5.x - Host Mac OS Sierra 10.12.5 - Guest Windows 7 Ultimate

Reported by: fserrano Owned by:
Component: network Version: VirtualBox 5.1.24
Keywords: Mac OS X Sierra, Oracle 12c, Windows 7, connection problem Cc:
Guest type: Windows Host type: Mac OS X

Description

I am using a host Mac OS X Sierra 10.12.5 and I have a guest with Windows 7 Ultimate installed and I can not connect from the host to the Oracle 12c R1 installed on the guest. I also have MySQL and DB2 installed in the guest and I can connect to both of then with no problem. Windows Firewall is off. The ping works with host pinging the guest. If I access Oracle from inside the guest it works ok also. I have already tryied to use NAT and Host-only Network adapters and none of them work. I have had this machine working since I used host Mac OS X Mountain Lion 10.8 with Vitualbox 4.3, it worked perfectly. When I updated to Mac OS X Sierra 10.12.5 I had to update the Virtualbox to 5 and than I started to have this problem that is still the same on Virtualbox 5.1.24. I have already tryied to install Windows 10 in Virtualbox 5.1.22 and had the same problem.

The error that I receive when I try to connect is: Status : Failure -Test failed: IO Error: The Network Adapter could not establish the connection.

Attachments (2)

VBox.log (66.5 KB ) - added by fserrano 7 years ago.
Machine full log
bug16944.pcap (352 bytes ) - added by fserrano 7 years ago.
bug16944.pcap

Download all attachments as: .zip

Change History (10)

by fserrano, 7 years ago

Attachment: VBox.log added

Machine full log

comment:1 by Valery Ushakov, 7 years ago

What is the port you expect it to listen on. What does netstat -n say?

comment:2 by fserrano, 7 years ago

I was expecting to listen on port 1521.

The netstat -n says:

Active Connections

Proto  Local Address      Foreign Address   State
TCP    127.0.0.1:1521     127.0.0.1:49169   ESTABLISHED
TCP    127.0.0.1:49169    127.0.0.1:1521    ESTABLISHED

comment:3 by Valery Ushakov, 7 years ago

Please, can you provide packet capture from the guest side taken while you try and fail to connect to the database from the host.

Start

tcpdump -w bug16944.pcap -U tcp port 1521

in the guest and then try to connect from the host. After connection fails, kill the tcpdump with ^C.

by fserrano, 7 years ago

Attachment: bug16944.pcap added

bug16944.pcap

comment:4 by fserrano, 7 years ago

This is the packet capture:

12:58:41.468987 IP 192.168.56.1.51465 > Fernando-VM.1521: Flags [SEW], seq 3266717134, win 65535, options [mss 1460,nop,wscale 5,nop,nop,TS val 141447249 ecr 0,
sackOK,eol], length 0
12:58:41.468987 IP Fernando-VM.1521 > 192.168.56.1.51465: Flags [R.], seq 0, ack 3266717135, win 0, length 0
12:59:01.937737 IP 192.168.56.1.51466 > Fernando-VM.1521: Flags [SEW], seq 3607682835, win 65535, options [mss 1460,nop,wscale 5,nop,nop,TS val 141467644 ecr 0,
sackOK,eol], length 0
12:59:01.937737 IP Fernando-VM.1521 > 192.168.56.1.51466: Flags [R.], seq 0, ack 3607682836, win 0, length 0
^C

I tried to connect twice.

comment:5 by Valery Ushakov, 7 years ago

Sorry what I mean to ask was the output of netstat -an (note the -a). It looks like your oracle instance only listens on the loopback.

comment:6 by fserrano, 7 years ago

No problem. This is the netstat -an:

Active Connections

  Proto  Local Address          Foreign Address        State
  TCP    0.0.0.0:135            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:445            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:523            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:554            0.0.0.0:0              LISTENING
  TCP    0.0.0.0:2869           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:3389           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5357           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:5500           0.0.0.0:0              LISTENING
  TCP    0.0.0.0:10243          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49152          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49153          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49154          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49155          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49168          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49178          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:49179          0.0.0.0:0              LISTENING
  TCP    0.0.0.0:50000          0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1521         0.0.0.0:0              LISTENING
  TCP    127.0.0.1:1521         127.0.0.1:49169        ESTABLISHED
  TCP    127.0.0.1:49156        0.0.0.0:0              LISTENING
  TCP    127.0.0.1:49169        127.0.0.1:1521         ESTABLISHED
  TCP    192.168.56.105:139     0.0.0.0:0              LISTENING
  TCP    192.168.58.106:2030    0.0.0.0:0              LISTENING
  TCP    [::]:135               [::]:0                 LISTENING
  TCP    [::]:445               [::]:0                 LISTENING
  TCP    [::]:523               [::]:0                 LISTENING
  TCP    [::]:554               [::]:0                 LISTENING
  TCP    [::]:2869              [::]:0                 LISTENING
  TCP    [::]:3389              [::]:0                 LISTENING
  TCP    [::]:3587              [::]:0                 LISTENING
  TCP    [::]:5357              [::]:0                 LISTENING
  TCP    [::]:5500              [::]:0                 LISTENING
  TCP    [::]:10243             [::]:0                 LISTENING
  TCP    [::]:49152             [::]:0                 LISTENING
  TCP    [::]:49153             [::]:0                 LISTENING
  TCP    [::]:49154             [::]:0                 LISTENING
  TCP    [::]:49155             [::]:0                 LISTENING
  TCP    [::]:49168             [::]:0                 LISTENING
  TCP    [::]:49178             [::]:0                 LISTENING
  TCP    [::]:49179             [::]:0                 LISTENING
  TCP    [::]:50000             [::]:0                 LISTENING
  TCP    [fe80::51c:683b:3b7f:94d0%17]:2030  [::]:0                 LISTENING
  UDP    0.0.0.0:123            *:*
  UDP    0.0.0.0:500            *:*
  UDP    0.0.0.0:523            *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:3702           *:*
  UDP    0.0.0.0:4500           *:*
  UDP    0.0.0.0:5004           *:*
  UDP    0.0.0.0:5005           *:*
  UDP    0.0.0.0:5355           *:*
  UDP    0.0.0.0:53680          *:*
  UDP    0.0.0.0:54189          *:*
  UDP    0.0.0.0:58404          *:*
  UDP    0.0.0.0:63169          *:*
  UDP    0.0.0.0:63257          *:*
  UDP    127.0.0.1:1900         *:*
  UDP    127.0.0.1:61158        *:*
  UDP    192.168.56.105:137     *:*
  UDP    192.168.56.105:138     *:*
  UDP    192.168.56.105:1900    *:*
  UDP    192.168.56.105:61157   *:*
  UDP    [::]:123               *:*
  UDP    [::]:500               *:*
  UDP    [::]:3540              *:*
  UDP    [::]:3702              *:*
  UDP    [::]:3702              *:*
  UDP    [::]:4500              *:*
  UDP    [::]:5004              *:*
  UDP    [::]:5005              *:*
  UDP    [::]:5355              *:*
  UDP    [::]:63170             *:*
  UDP    [::]:63258             *:*
  UDP    [::1]:1900             *:*
  UDP    [::1]:61156            *:*
  UDP    [fe80::51c:683b:3b7f:94d0%17]:1900  *:*
  UDP    [fe80::51c:683b:3b7f:94d0%17]:61155  *:*
Last edited 7 years ago by fserrano (previous) (diff)

comment:7 by Valery Ushakov, 7 years ago

Resolution: invalid
Status: newclosed

Thanks and my apologies again. So, right, as I expected it's listening only on the loopback:

TCP    127.0.0.1:1521         0.0.0.0:0              LISTENING

so this is a problem with configuration of your Oracle instance.

You can check that your MySQL and DB2 are listening on 0.0.0.0:port (whatever their port numbers are), which is a wildcard address - so you can connect to them from outside the VM.

comment:8 by fserrano, 7 years ago

Thank you vushakov!!! Its is strange because it has changed when I updated...

Note: See TracTickets for help on using tickets.

© 2023 Oracle
ContactPrivacy policyTerms of Use