ESXi

 View Only
  • 1.  VMware Upgrades and Samba Shares

    Posted Feb 08, 2010 02:54 PM

    I just upgraded VMware Tools and VMware hardware to 7 on a vm that's hosting samba shares. This morning, users are saying they can't access the shares anymore. Anyone seen this? I haven't been able to figure out what could have changed.

    Thanks,

    Scott



  • 2.  RE: VMware Upgrades and Samba Shares

    Posted Feb 08, 2010 02:56 PM

    Check if your network setup/virtual NIC has gone in the guest. That happens when you upgrade to HW 7. You first need to update the VMware Tools and then the hardware. But even then I got some machines which lost their "old" vNIC and got a "new" unconfigured one.


    AWo

    VCP 3 & 4

    Author @ vmwire.net

    \[:o]===\[o:]

    =Would you like to have this posting as a ringtone on your cell phone?=

    =Send "Posting" to 911 for only $999999,99!=



  • 3.  RE: VMware Upgrades and Samba Shares

    Posted Feb 08, 2010 03:21 PM

    Thanks for your response.

    I know I've had to remove the "ghost" nics on the windows boxes we upgrades, but I have no idea how to check the virtual NIC on linux. Can you explain how to do this?

    Thanks a lot.

    Scott



  • 4.  RE: VMware Upgrades and Samba Shares

    Posted Feb 08, 2010 03:22 PM

    Login as "root" and run "ifconfig -a". Post that.


    AWo

    VCP 3 & 4

    Author @ vmwire.net

    \[:o]===\[o:]

    =Would you like to have this posting as a ringtone on your cell phone?=

    =Send "Posting" to 911 for only $999999,99!=



  • 5.  RE: VMware Upgrades and Samba Shares

    Posted Feb 08, 2010 03:29 PM

    Here you go. And just an FYI - I can putty into it and the other networking components seem to be ok. Thanks.

    # ifconfig -a

    eth0 Link encap:Ethernet HWaddr 00:50:56:98:42:A9

    inet addr:10.150.1.85 Bcast:10.150.1.255 Mask:255.255.255.0

    inet6 addr: fe80::250:56ff:fe98:42a9/64 Scope:Link

    UP BROADCAST RUNNING MULTICAST MTU:1500 Metric:1

    RX packets:767303 errors:0 dropped:0 overruns:0 frame:0

    TX packets:98068 errors:0 dropped:0 overruns:0 carrier:0

    collisions:0 txqueuelen:1000

    RX bytes:91422337 (87.1 MiB) TX bytes:16680179 (15.9 MiB)

    Interrupt:59 Base address:0x2024

    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:1861 errors:0 dropped:0 overruns:0 frame:0

    TX packets:1861 errors:0 dropped:0 overruns:0 carrier:0

    collisions:0 txqueuelen:0

    RX bytes:2793044 (2.6 MiB) TX bytes:2793044 (2.6 MiB)

    sit0 Link encap:IPv6-in-IPv4

    NOARP MTU:1480 Metric:1

    RX packets:0 errors:0 dropped:0 overruns:0 frame:0

    TX packets:0 errors:0 dropped:0 overruns:0 carrier:0

    collisions:0 txqueuelen:0

    RX bytes:0 (0.0 b) TX bytes:0 (0.0 b)



  • 6.  RE: VMware Upgrades and Samba Shares

    Posted Feb 08, 2010 03:41 PM

    At least I can see one active vNIC. And if you can ssh into the server networking is running in general.

    You need to check

    • if that is the adapter samba uses

    • if samba is running
      /etc/init.d/nmb status
      /etc/init.d/smb status
      and maybe /etc/init.d/winbind status

    AWo

    VCP 3 & 4

    Author @ vmwire.net

    \[:o]===\[o:]

    =Would you like to have this posting as a ringtone on your cell phone?=

    =Send "Posting" to 911 for only $999999,99!=



  • 7.  RE: VMware Upgrades and Samba Shares

    Posted Feb 08, 2010 03:56 PM

    It looks like all those services are running fine. And that's the adapter that samba is using. I don't know what else to look at. It doesn't make any sense why this would have just stopped working after the VMware upgrades.



  • 8.  RE: VMware Upgrades and Samba Shares

    Posted Feb 09, 2010 08:50 AM

    Try "smbclient -L 127.0.0.1" and "smbclient -L

    =Send "Posting" to 911 for only $999999,99!=



  • 9.  RE: VMware Upgrades and Samba Shares

    Posted Feb 18, 2010 09:53 PM

    I ended up having to upgrade Samab. Not sure if it was related, but thanks for your help.