Direct-connect inside network with dynamically assigned IP-addresses

I have 13+GiB of files to transfer between two computers (one arch and one Win7) and would rather not spend the day moving them ~1GiB at a time via flashdrives.
I have tried setting up an ad-hoc network on the win7 machine, but wifi-menu fails to connect to it.
I have tried setting up an ssh server on the arch machine and accessing it via PuTTY on the Win7 machine.
I have tried setting up an apache server on the arch machine and accessing it via firefox on the Win7 machine.
I do not have the permissions to statically assign ip addresses on the network, and need to somehow directly connect between these two computers.  Any suggestions?

5donuts wrote:I've spent the last hour or so trying to set up samba, but I can't figure out how to connect to a Windows shared folder with smbclient, and just cd-ing into the mountpoint doesn't work since access is denied
Post the exact commands that you are using and the exact error messages that you receive.
For mounting windows shares I use variations of the following command:
mount -t cifs //<windows ip address or host name>/<windows share name> /mnt/foo -o nosetuids,uid=<your local user id>,gid=<your local group id>,user=<windows user name>,workgroup=<windows workgroup>
Have you tried something similar? It should "just work".

Similar Messages

  • Moving Time Machine Drive from Direct Connect to Network Share

    I have a 1 TB external USB 2 drive I use for my Time Machine backup. I'd like to move that drive to a file server and continue backing up to it. The problem appears to be that when backing up to the drive as a network volume, Time Machine wants to create a new sparsebundle for the backup and not use the existing TM backup folder on the drive.
    Is it possible to migrate a Time Machine drive from direct connect to network while preserving the backed up data? Thanks!

    Kenneth Kirksey wrote:
    I have a 1 TB external USB 2 drive I use for my Time Machine backup. I'd like to move that drive to a file server and continue backing up to it.
    Depending on what "file server" you're using, that may or may not work reliably. Here's the criteria they must meet: Disks that can be used with Time Machine. And be careful here: just because some 3rd-party hardware claims to support Time Machine doesn't necessarily mean that Apple supports it, or that it will work in all circumstances.
    The problem appears to be that when backing up to the drive as a network volume, Time Machine wants to create a new sparsebundle for the backup and not use the existing TM backup folder on the drive.
    That's correct.
    Is it possible to migrate a Time Machine drive from direct connect to network while preserving the backed up data? Thanks!
    See #18 in Time Machine - Frequently Asked Questions (or use the link in *User Tips* at the top of this forum).

  • HT4972 can't connect to network with linksys e2500

    Can't connect to network with linksys E2500. Can anyone help me?

    Look at iOS Troubleshooting Wi-Fi networks and connections  http://support.apple.com/kb/TS1398
    iPad: Issues connecting to Wi-Fi networks  http://support.apple.com/kb/ts3304
    iOS: Recommended settings for Wi-Fi routers and access points  http://support.apple.com/kb/HT4199
    Additional things to try.
    Try this first. Turn Off your iPad. Then turn Off (disconnect power cord) the wireless router & then back On. Now boot your iPad. Hopefully it will see the WiFi.
    Go to Settings>Wi-Fi and turn Off. Then while at Settings>Wi-Fi, turn back On and chose a Network.
    Change the channel on your wireless router. Instructions at http://macintoshhowto.com/advanced/how-to-get-a-good-range-on-your-wireless-netw ork.html
    Another thing to try - Go into your router security settings and change from WEP to WPA with AES.
    How to Quickly Fix iPad 3 Wi-Fi Reception Problems
    http://osxdaily.com/2012/03/21/fix-new-ipad-3-wi-fi-reception-problems/
    If none of the above suggestions work, look at this link.
    iPad Wi-Fi Problems: Comprehensive List of Fixes
    http://appletoolbox.com/2010/04/ipad-wi-fi-problems-comprehensive-list-of-fixes/
    Fix iPad Wifi Connection and Signal Issues  http://www.youtube.com/watch?v=uwWtIG5jUxE
    Unable to Connect After iOS Update - saw this solution on another post.
    https://discussions.apple.com/thread/4010130?tstart=60
    Note - When troubleshooting wifi connection problems, don't hold your iPad by hand. There have been a few reports that holding the iPad by hand, seems to attenuate the wifi signal.
    ~~~~~~~~~~~~~~~
    If any of the above solutions work, please post back what solved your problem. It will help others with the same problem.
     Cheers, Tom

  • Network computers auto assigning IP address

    I'm administering 300+ MacBook in a 1 to 1 class room setting. for 3 months I had no problems, but more and more laptops are coming up with self-assigned IP address with no warning or reason. users (students and teachers) do not have admin authority to change settings so when it happens I have to physically (can't vnc to a deadend...) go and set TCP/IP to automatic and apply.
    Previous years we used windows platform laptops and never had this issue so I'm hesitent to think its DHCP running out of lease IPs (I've checked it too)
    If lowering the lease time so that if a student DOES self assign IP it wont be for long is a solution I'd be able to do so, but it seems rediculous to me that with DHCP, proper net setup, and adaquate wireless access point coverage (on uninterfering channels) that the macbook would rather make up some random garbage IP then just keep trying at DHCP....
    the self assigned IP isn't even in the ip range so even if it DID do it network connection would never work anyway.
    Any idea what I can do to NOT have the macbooks go auto assign IP (which is the dumbest thing I've ever seen) and keep their dhcp lease intact or reassign?

    Welcome to Apple Discussions:
    A "self-assigned" IP means that the computer is not able to reach the DHCP server.
    There is nothing "dumb" about it if you understand how networking works. It's a flag that something is wrong with the network and the computer is not connected to anything.
    Of course the "self-assigned" IP is not in your network IP range. That's how it works.
    If this problem is new, and you have not done anything, it may well be local RF interference blocking or jamming the WiFi signal.
    You might consider installing some sniffers on a computer and checking what other signals are in the area that may be causing the problem. Anything from a leaky microwave oven, to student(s) using a cellphone(s) or BlueTooth devices can cause WiFi issues. Being near an airport, a fire or police station or other source or RF can also cause loss of signal.

  • Inside lan is not reachable even after cisco Remote access vpn client connected to router C1841 But can ping to the router inside interface and loop back interface but not able to ping even to the directly connected inside device..??

    Hii frnds,
    here is the configuration in my router C1841..for the cisco ipsec remote access vpn..i was able to establish a vpn session properly...but there after i can only reach up to the inside interfaces of the router..but not to the lan devices...
    Below is the out put from the router
    r1#sh run
    Building configuration...
    Current configuration : 3488 bytes
    ! Last configuration change at 20:07:20 UTC Tue Apr 23 2013 by ramana
    ! NVRAM config last updated at 11:53:16 UTC Sun Apr 21 2013 by ramana
    version 15.1
    service config
    service timestamps debug datetime msec
    service timestamps log datetime msec
    no service password-encryption
    hostname r1
    boot-start-marker
    boot-end-marker
    enable secret 5 $1$6RzF$L6.zOaswedwOESNpkY0Gb.
    aaa new-model
    aaa authentication login local-console local
    aaa authentication login userauth local
    aaa authorization network groupauth local
    aaa session-id common
    dot11 syslog
    ip source-route
    ip cef
    ip domain name r1.com
    multilink bundle-name authenticated
    license udi pid CISCO1841 sn FHK145171DM
    username ramana privilege 15 secret 5 $1$UE7J$u9nuCPGaAasL/k7CxtNMj.
    username giet privilege 15 secret 5 $1$esE5$FD9vbBwTgHERdRSRod7oD.
    redundancy
    crypto isakmp policy 10
    encr 3des
    authentication pre-share
    group 2
    crypto isakmp client configuration group ra-vpn
    key xxxxxx
    domain r1.com
    pool vpn-pool
    acl 150
    save-password
      include-local-lan
    max-users 10
    crypto ipsec transform-set my-vpn esp-3des esp-md5-hmac
    crypto dynamic-map RA 1
    set transform-set my-vpn
    reverse-route
    crypto map ra-vpn client authentication list userauth
    crypto map ra-vpn isakmp authorization list groupauth
    crypto map ra-vpn client configuration address respond
    crypto map ra-vpn 1 ipsec-isakmp dynamic RA
    interface Loopback0
    ip address 10.2.2.2 255.255.255.255
    interface FastEthernet0/0
    bandwidth 8000000
    ip address 117.239.xx.xx 255.255.255.240
    no ip redirects
    no ip unreachables
    no ip proxy-arp
    ip nat outside
    ip virtual-reassembly
    duplex auto
    speed auto
    crypto map ra-vpn
    interface FastEthernet0/1
    description $ES_LAN$
    ip address 192.168.10.252 255.255.255.0 secondary
    ip address 10.10.10.1 255.255.252.0 secondary
    ip address 172.16.0.1 255.255.252.0 secondary
    ip address 10.10.7.1 255.255.255.0
    ip nat inside
    ip virtual-reassembly
    duplex auto
    speed auto
    ip local pool vpn-pool 172.18.1.1   172.18.1.100
    ip forward-protocol nd
    ip http server
    ip http authentication local
    no ip http secure-server
    ip dns server
    ip nat pool INTERNETPOOL 117.239.xx.xx 117.239.xx.xx netmask 255.255.255.240
    ip nat inside source list 100 pool INTERNETPOOL overload
    ip route 0.0.0.0 0.0.0.0 117.239.xx.xx
    access-list 100 permit ip 10.10.7.0 0.0.0.255 any
    access-list 100 permit ip 10.10.10.0 0.0.1.255 any
    access-list 100 permit ip 172.16.0.0 0.0.3.255 any
    access-list 100 permit ip 192.168.10.0 0.0.0.255 any
    access-list 150 permit ip 10.10.7.0 0.0.0.255 172.18.0.0 0.0.255.255
    access-list 150 permit ip host 10.2.2.2 172.18.1.0 0.0.0.255
    access-list 150 permit ip 192.168.10.0 0.0.0.255 172.18.1.0 0.0.0.255
    control-plane
    line con 0
    login authentication local-console
    line aux 0
    line vty 0 4
    login authentication local-console
    transport input telnet ssh
    scheduler allocate 20000 1000
    end
    r1>sh ip route
    Codes: L - local, C - connected, S - static, R - RIP, M - mobile, B - BGP
           D - EIGRP, EX - EIGRP external, O - OSPF, IA - OSPF inter area
           N1 - OSPF NSSA external type 1, N2 - OSPF NSSA external type 2
           E1 - OSPF external type 1, E2 - OSPF external type 2
           i - IS-IS, su - IS-IS summary, L1 - IS-IS level-1, L2 - IS-IS level-2
           ia - IS-IS inter area, * - candidate default, U - per-user static route
           o - ODR, P - periodic downloaded static route, + - replicated route
    Gateway of last resort is 117.239.xx.xx to network 0.0.0.0
    S*    0.0.0.0/0 [1/0] via 117.239.xx.xx
          10.0.0.0/8 is variably subnetted, 5 subnets, 3 masks
    C        10.2.2.2/32 is directly connected, Loopback0
    C        10.10.7.0/24 is directly connected, FastEthernet0/1
    L        10.10.7.1/32 is directly connected, FastEthernet0/1
    C        10.10.8.0/22 is directly connected, FastEthernet0/1
    L        10.10.10.1/32 is directly connected, FastEthernet0/1
          117.0.0.0/8 is variably subnetted, 2 subnets, 2 masks
    C        117.239.xx.xx/28 is directly connected, FastEthernet0/0
    L        117.239.xx.xx/32 is directly connected, FastEthernet0/0
          172.16.0.0/16 is variably subnetted, 2 subnets, 2 masks
    C        172.16.0.0/22 is directly connected, FastEthernet0/1
    L        172.16.0.1/32 is directly connected, FastEthernet0/1
          172.18.0.0/32 is subnetted, 1 subnets
    S        172.18.1.39 [1/0] via 49.206.59.86, FastEthernet0/0
          192.168.10.0/24 is variably subnetted, 2 subnets, 2 masks
    C        192.168.10.0/24 is directly connected, FastEthernet0/1
    L        192.168.10.252/32 is directly connected, FastEthernet0/1
    r1#sh crypto isakmp sa
    IPv4 Crypto ISAKMP SA
    dst             src             state          conn-id status
    117.239.xx.xx   49.206.59.86    QM_IDLE           1043 ACTIVE
    IPv6 Crypto ISAKMP SA
    r1 #sh crypto ipsec sa
    interface: FastEthernet0/0
        Crypto map tag: giet-vpn, local addr 117.239.xx.xx
       protected vrf: (none)
       local  ident (addr/mask/prot/port): (0.0.0.0/0.0.0.0/0/0)
       remote ident (addr/mask/prot/port): (172.18.1.39/255.255.255.255/0/0)
       current_peer 49.206.59.86 port 50083
         PERMIT, flags={}
        #pkts encaps: 0, #pkts encrypt: 0, #pkts digest: 0
        #pkts decaps: 2, #pkts decrypt: 2, #pkts verify: 2
        #pkts compressed: 0, #pkts decompressed: 0
        #pkts not compressed: 0, #pkts compr. failed: 0
        #pkts not decompressed: 0, #pkts decompress failed: 0
        #send errors 0, #recv errors 0
         local crypto endpt.: 117.239.xx.xx, remote crypto endpt.: 49.206.xx.xx
         path mtu 1500, ip mtu 1500, ip mtu idb FastEthernet0/0
         current outbound spi: 0x550E70F9(1427009785)
         PFS (Y/N): N, DH group: none
         inbound esp sas:
          spi: 0x5668C75(90606709)
            transform: esp-3des esp-md5-hmac ,
            in use settings ={Tunnel UDP-Encaps, }
            conn id: 2089, flow_id: FPGA:89, sibling_flags 80000046, crypto map: ra-vpn
            sa timing: remaining key lifetime (k/sec): (4550169/3437)
            IV size: 8 bytes
            replay detection support: Y
            Status: ACTIVE
         inbound ah sas:
         inbound pcp sas:
         outbound esp sas:
          spi: 0x550E70F9(1427009785)
            transform: esp-3des esp-md5-hmac ,
            in use settings ={Tunnel UDP-Encaps, }
            conn id: 2090, flow_id: FPGA:90, sibling_flags 80000046, crypto map: ra-vpn
            sa timing: remaining key lifetime (k/sec): (4550170/3437)
            IV size: 8 bytes
            replay detection support: Y
            Status: ACTIVE
         outbound ah sas:
         outbound pcp sas:

    hi  Maximilian Schojohann..
    First i would like to Thank you for showing  interest in solving my issue...After some research i found that desabling the " IP CEF" will solve the issue...when i desable i was able to communicate success fully with the router lan..But when i desable " IP CEF "  Router cpu processer goes to 99% and hangs...
    In the output of " sh process cpu" it shows 65% of utilization from "IP INPUT"
    so plz give me an alternate solution ....thanks in advance....

  • Can't connect to internet..self assigned ip address problem with DSL Modem

    I've run into this before, without resolution, and now again on a friend's iMac. Time to ask around...
    Basically, everything appears to be assigned and configured perfectly, but the network status always shows, "...you have a self assigned IP address and may not be able to connect to the internet". Sure can't connect to the net when it says that.
    I've gone thru the procedure advise before that details the sequence of events needed to insure the modem resets and recognizes the Mac and it's incoming DSL (sbcglobal) signal. The order of network priority is set properly by dragging built in ethernet to the top of the list. Modem was powered down, plugged in, and then connected to the Mac, but no solution. Any ideas? thanks

    This continues to be a mystery. I've had my powerbook on several networks, and connection has, most of the time, been an automatic process. Additionally, I've installed new systems for people with the same isp, and all has been well. So easy is the process, it's never been an issue. However, following explicit procedural instructions (including powering the Mac down), has proven unsuccessful on 2 different occasions.
    There is little help with the isp support in India, which is where the call routes too.
    The only thing I have not done is to swap out the cable at one of the locations, but the other location, which has the same issue, works fine on the iMac there. Only when I connect my Powerbook to the modem, does the "...self assigned ip address...not be able to connect to the internet" appear.
    I just keep thinking there has got to be a small detail that is being overlooked.

  • Direct connect NFS/CIFS with 1.4

    I see how 1.4's appliance ports can help with direct connect multipath iSCSI. Each fabric gets a VLAN/subnet, iSCSI has multiple targets via each fabric, etc.
    But I don't see how appliance ports help with direct connect NFS/CIFS. E.g.,
    In this diagram, traffic from hosts active on fabric B must go over the northbound LAN to reach the NAS. Even if every host and appliance has its NIC failover configured to prefer fabric A and perform preemption, you'll still have failures like NAS NIC's and IOM's that will cause some/all NAS traffic to go across the northbound LAN. Thus, you've got one of two situations:
        1) The LAN can handle the NAS traffic. If so, why not plug the NAS into the LAN in the first place?
        2) The LAN cannot handle the traffic, in which case you haven't built real fault-tolerance and, worse, a UCS problem can impact the LAN.
    Am I missing something here? How are appliance ports better than using switch mode, shown below?

    Yes - you have a valid point on the traffic pattern depending on what fails etc.
    Just to back up for a moment..
    Version 1.3 and below has 2 types of Ethernet ports - Uplink and Server port.
    Version 1.4 has 4 types of Ethernet ports - Uplink, Server, Appliance, Monitoring port
    In 1.3, to directly connecting a NAS to the FI's meant that you move to switch mode on the FI's and then set the port connecting to the NAS as an uplink port. What that did is that the port connecting to the NAS was a a trunk port at the FI end allowing all VLANs (i.e no VLAN filtering), no QoS settings etc.
    So if you wanted to stay in End Host mode AND not liking the above caveats, you connected the NAS to an upstream switch and not UCS and that option remains wit you today.
    What the appliance port gives you now is that the VLAN(s) the NAS belongs to can be filtered, QoS settings possible and most importantly, it works in End Host Mode (most deployments are based on it).
    The above is the rationale for the Appliance port and the port type was neeeded even if it works today in switch mode.
    Now the question comes, appliance port in EHM or Switch mode (which is what the question is).
    In EHM you are right, east-west traffic between NAS-blades could utilize the upstream network.
    You can design efficiently by specifying the fabric id (A or B as primary) or set fabric affinity if using a soft switch but  guaranteed total localization (not using upstream network) cannot be made as you correctly said depending on "what" fails.
    If all the uplinks on A fail, yes the whole thing should fail over but if a link between the IOM and the FI fails, then the servers pinned to that link will start using the external network.
    So yes, the network needs to be designed keeping the flows and what if scenarios in mind. East-west traffic not hitting upstream at all cannot be assumed.
    The long term solution is to have data links between the FI's in EHM or they are vPC peers and hence both links to the NAS from the FI's will be active/active.
    Appliance port in switch mode can be used but that also depends on which links are STP blocked etc to guarantee that.
    The topology you mentioned does that ..but then you also need to keep in mind on failurea what happens etc i.e the ISL between the FI's should always be forwarding for that VLAN.
    Thanks
    --Manish

  • Proxy client (over USB connection) with DHCP assigned IP address doesn't work with FRDM-K64F

    Hello,
    after reading about the issues on this forum with a static IP address on the Freescale FRDM-K64F board I went for an DHCP address but I can't get the proxy client to work over a USB connection with DHCP either.
    My console tells me the following:
    RTC Time: Wed 2014-01-01 00:07:27
    Network initialized
    IP Address:      10.143.xxx.yyy (xxx and yyy is real numbers, just changing them for the forum to letters)
    Subnet mask:     255.255.252.0
    Gateway:         10.143.xxx.yyy
    MAC-address:     00:0c:00:06:70:00
    And when I try o to connect with the following command :
    java -jar proxy.jar -socket 10.143.xxx.yyy
    I get the following output and no CLI interface:
    Trying to open socket connection with device: 10.143.xxx.yyy:2201
    Connected to the socket: Socket[addr=/10.143.xxx.yyy,port=2201,localport=49605]
    Open channel 8 with hash 0x130399b3
    Channel 8 CLOSED -> OPENED
    notifyResponse AVAILABLE_RESPONSE on channel 8
    Channel 8 OPENED -> AVAILABLE
    Open channel 9 with hash 0x0
    Channel 8 AVAILABLE -> REQUEST_SENT
    notifyResponse ACK_RESPONSE on channel 8
    Channel 8 REQUEST_SENT -> ACKNOWLEDGED
    Channel 8 ACKNOWLEDGED -> DATA_SENT
    notifyResponse AVAILABLE_RESPONSE on channel 8
    Channel 8 DATA_SENT -> AVAILABLE
    Channel 8 AVAILABLE -> REQUEST_SENT
    notifyResponse ACK_RESPONSE on channel 8
    Channel 8 REQUEST_SENT -> ACKNOWLEDGED
    Channel 8 ACKNOWLEDGED -> DATA_SENT
    notifyResponse AVAILABLE_RESPONSE on channel 8
    Channel 8 DATA_SENT -> AVAILABLE
    Channel 8 AVAILABLE -> REQUEST_SENT
    notifyResponse ACK_RESPONSE on channel 8
    Channel 8 REQUEST_SENT -> ACKNOWLEDGED
    Channel 8 ACKNOWLEDGED -> DATA_SENT
    notifyResponse AVAILABLE_RESPONSE on channel 8
    Channel 8 DATA_SENT -> AVAILABLE
    Channel 8 AVAILABLE -> REQUEST_SENT
    notifyResponse ACK_RESPONSE on channel 8
    Channel 8 REQUEST_SENT -> ACKNOWLEDGED
    Channel 8 ACKNOWLEDGED -> DATA_SENT
    notifyResponse AVAILABLE_RESPONSE on channel 8
    Channel 8 DATA_SENT -> AVAILABLE
    Channel 8 AVAILABLE -> REQUEST_SENT
    notifyResponse ACK_RESPONSE on channel 8
    Channel 8 REQUEST_SENT -> ACKNOWLEDGED
    Channel 8 ACKNOWLEDGED -> DATA_SENT
    notifyResponse AVAILABLE_RESPONSE on channel 8
    Channel 8 DATA_SENT -> AVAILABLE
    Channel 8 AVAILABLE -> REQUEST_SENT
    notifyResponse ACK_RESPONSE on channel 8
    Channel 8 REQUEST_SENT -> ACKNOWLEDGED
    Channel 8 ACKNOWLEDGED -> DATA_SENT
    notifyResponse AVAILABLE_RESPONSE on channel 8
    Channel 8 DATA_SENT -> AVAILABLE
    Channel 8 AVAILABLE -> REQUEST_SENT
    notifyResponse ACK_RESPONSE on channel 8
    Channel 8 REQUEST_SENT -> ACKNOWLEDGED
    Channel 8 ACKNOWLEDGED -> DATA_SENT
    notifyResponse AVAILABLE_RESPONSE on channel 8
    Channel 8 DATA_SENT -> AVAILABLE
    Channel 8 AVAILABLE -> REQUEST_SENT
    notifyResponse ACK_RESPONSE on channel 8
    Channel 8 REQUEST_SENT -> ACKNOWLEDGED
    Channel 8 ACKNOWLEDGED -> DATA_SENT
    notifyResponse AVAILABLE_RESPONSE on channel 8
    Channel 8 DATA_SENT -> AVAILABLE
    I don't know if this matter but my java version is:
    java version "1.8.0_31"
    Java(TM) SE Runtime Environment (build 1.8.0_31-b13)
    Java HotSpot(TM) 64-Bit Server VM (build 25.31-b07, mixed mode)
    Any ideas or am I missing something completely?
    Thanks
    Andy

    Hi, Andy. Please excuse my ignorance, I am very new at this ME embedded stuff. I had my challenges, but was finally able to get my board up with a static address. I went through a lot of headaches, but finally got the board flashed with the latest bin. I then updated the jwc_properties.ini file on the SD card to include:
    # Whether static configuration or DHCP server is used do get IP address. Possible values: dhcp,static
    ip.method = static
    # IP address,used with static IP configuration only
    ip.addr = 192.168.0.30
    # Network mask,used with static IP configuration only
    ip.netmask = 255.255.255.0
    # Network gateway,used with static IP configuration only
    ip.gateway = 192.168.0.1
    # DNS server,used with static IP configuration only
    ip.dns = 208.67.222.222
    # MAC address
    mac.addr = 01:02:03:04:05:06
    I was then put the card into the board, disconnected both USB cables, and then powered it up. From that point I was able to ping the board. I can now use Device Manager in NetBeans to connect to the device.
    I am struggling quite a bit with many issues. It seems that when I try to stop the app from NetBeans, the "please wait" dialog hangs forever. I have to use Windows Task Manager to kill the "JavaW" process tree and reconnect the board.
    I have also had trouble understanding the GPIO pin assignments. Another gotcha was trying to use the AutoStart feature. Since the sample app never cleanly exited, I thought that I bricked the board. The secret is to power it down, remove the SD card, and then delete all files EXCEPT the jwc_properties.ini file, put the SD card back in, then power up. It seems that the board forgets that the MIDlet was installed.
    Hope this helps others out there.
    Please everybody, post your experiences here. There seem to be very few of us, and finding pearls in the dust is rare right now.
    Regards,
    Pete

  • Unable to connect to network with Safari and Software Update

    A user I support has encountered a problem with networking. He is unable to connect to the network with Safari and Software Update, but IS able to connect and surf with Foxfire and some other programs. Another unusual symptom is that he actually can connect to one web site (which is in his Bookmarks Bar) with Safari, but can't connect to anything else. He's also unable to navigate off of that one site he connects to. When he runs Network Diagnostics, he gets all green lights (no problems). He has fixed permissions, deleted Safari Cache and .plist, rebooted - not fixed yet. He's using 10.4.8 on a PowerPC G4. Any ideas appreciated (this is the wierdest I've seen in a while!).

    Here's what he did. After reading your post, he created another location in his network preferences, entering EXACTLY the same info that was in his old location (he even used the old DNS addresses), except using a new location name. Then he chose the new location and "everything worked". It's one of life's great mysteries. Thanks for your help - it is appreciated.

  • Connected to network with no internet

    Ok so this is an interesting situation...
    We have two networks in two building across from each other. I can connect to network 1 with no problem and access the internet.
    On network 2, however, I can only get on the LAN and do not have complete internet access...as of a this morning. I changed nothing between last night and this morning (perhaps windows updates???). In fact, I checked my email this morning and then when I
    came back, could no longer access the internet.
    I have full access to the LAN on network 2, I can ping websites, but cannot use a browser to visit sites. I have done all the ipconfig release/renew/dnsflush commands that I know of/found on these forums. Other people DO NOT have this problem. It is just
    my computer.
    Any help is much appreciated!

    Hi,
    Did you set any proxy?
    If you can ping a host but not open it in a browser, then I suspect that your browser settings have been compromised. Check for any proxy settings that may have been configured by malware.
    Furthermore, please try to reset your Internet Explorer to check if the issue could be resolved:
    1. Close all Internet Explorer windows that are currently open.
    2. Open the desktop, and then tap or click the Internet Explorer  icon on the taskbar. Changing your settings will affect both Internet Explorer and Internet Explorer for the desktop.
    3. Tap or click the Tools button, and then tap or click
    Internet options.
    4. Tap or Click the Advanced tab, and then tap or click
    Reset.
    5. In the Reset Internet Explorer Settings dialog box, tap or click
    Reset.
    6. When Internet Explorer finishes applying default settings, tap or click
    Close, and then tap or click OK. You'll need to restart your PC for these changes to take effect.
    Karen Hu
    TechNet Community Support

  • Is it possible to directly connect two Xserves with a Promise VTrak E610fD via Fibre?

    I have two Xserves and I'd like to connect them with a Promise VTrak E610fD. As this storage has two controllers, I'd like to connect both Xserve with both controllers. Is this setup possible? Can I access (read and write) the same disk array with both Xserves simultaneously (Xsan?) or do I have to create two separate arrays?

    Hello bleistift, and welcome to the AppleBoards,
    Fibre channel is SCSI which means that any device connected by fibre assumes it is in sole control of that device. When you attach more than one machine via fibre both machines assume they are in control and unexpected behaviors and data corruption ensues. SAN (like Apple's XSAN) provides a layer of arbitration over the shares allowing multiple fibre connections to play nicely with one another while still being connected over fibre.
    You could easily connect two machines to a single RAID box if they are accessing different RAID volumes at the same time, but once you start connecting to the same data at the same time you need SAN.
    HTH,
    =Tod

  • Can't connect to network with mac, only pc.

    I have a powerbook and have just installed an airport extreme card. I do not have my own internet connection and intend to 'borrow' connections that I pick up.
    In the past I have used a friend's PC laptop &belkin wireless adapter to connect to networks accidentally found in both his house and mine. This was no problem whatsoever and a connection without passwords etc was possible in both.
    When I try to connect my powerbook the following happens:
    1. In his house: I can connect to an open apple network but the connection is unbearably slow while I can work on his computer from the same point relatively easily.
    2. In my house: When I try to connect I get 'error in connection to linksys' or similar (maybe even get asked for passwords).
    I have very limited knowledge of these things and have no idea what it means or what the problem is.
    If anyone can tell me why the connection always seems to be slow or unachievable on my powerbook (when an old PC laptop succeeds) I'd be most grateful.

    It could be as simple as the owners of those wireless networks didn''t want other people using their networks and have added a layer of security.
    One you may also want to have a look at these recent cases involving using other people's wireless networks.
    UK Case
    http://news.bbc.co.uk/1/hi/technology/4721723.stm
    US Case
    http://money.cnn.com/2005/07/07/technology/personaltech/wireless_arrest/

  • Airport Extreme wired network can't assign IP address, but wireless works

    *Problem details:*
    We have three computers intermittently on, wired into the ethernet LAN managed by the Airport Extreme.
    We have a few more computers that connect to the wireless network managed by the same Airport Extreme.
    As far as I know, no fancy settings hijinks have been attempted. I manage the router, and I only plugged the Airport into the cable modem and connected all the wires to the computers. The WiFi setup went a similar way -- I just turned it on and it sorted itself out. This was eight months ago, mind you -- everything has been going quite well up until this weekend.
    But! I got home from a trip this weekend to discover that all the machines that connected over the wired network could no longer get a connection to the internet. Any machine connected over the wireless network, however, was working just fine. Indeed, my macbook pros couldn't even see the Airport Extreme when I turned off their WiFi, connected them over Ethernet and opened the Airport Extreme configuration app!
    The wired machines complain that they have a self-assigned IP address. Sometimes, after resetting everything, they look like everything's fine for a moment. Like I said, ordinarily my macbook pro does not even recognize the router over the wired network. However, after reverting to factory defaults and restarting the Airport, the laptop did see it (until a few minutes went by and it realized something was wrong).
    I figured that renewing my DHCP lease would fix this problem, but it did not. Nor did turning off Passive FTP Mode (PASV) under Proxies in the Network configuration pane.
    I have tried resetting the router to factory defaults, power cycling the modem and router in various configurations, etc. but nothing has worked. In addition, I have verified that connecting any machine to the ethernet directly from the modem will work, so the problem is definitely being introduced by the Airport Extreme.
    So I guess my question is: what do I have to poke to return everything to normal? I'd like working wired and wireless networks again.
    *Some last few details:*
    The Airport is running 7.5.2, but downgrading to 7.4.2 produced no tangible difference.
    I have an Ubee D3.0 modem. All lights are green and blinky except the DS light, which is solid amber (and it is green when the modem is wired directly to one of my computers -- it's only amber when connected to the Airport).
    Some of the machines that can't connect to the wired network are PCs, so it's not just an OSX thing.
    My roommate's XBOX 360 can connect to the internet over the wired port. It doesn't have WiFi, so I'm pretty sure there's no way it could be fooling me.
    Thanks in advance for any advice you can muster.
    EDIT FOR APOLOGIES:
    I didn't realize I was posting this in the "Airport for Windows" section. While a Windows computer's connection is a concern, I would much rather get my Macs online and deal with that first. I can't figure out how to move the message myself.

    *An update:*
    Several days later, this issue seems to have fixed itself. I suspect there may have been Funny Business on my ISP's end (but then again, it's an ISP).

  • Can't connect wireless due to "self-assigned IP address"

    I recently switched from PC to Macbook. I cannot log on to many wifi networks I could previously access with my ThinkPad. The computer successfully finds the network and has a strong signal but will not connect. Under network status, I get a message that says something like "Your Macbook is connected to the wireless network but AirPort has a self-assigned IP address and may not be able to connect to the network."
    Ive tried various options but still no luck. This mostly happens in public Wi-Fi networks such as internet cafes, airports and Starbucks' T-Mobile networks. Thanks!

    Can you connect to any wireless location? Or does not fail only in certain places? If you can't connect anywhere, it is your problem. If you can connect in some places but not others, it is their problem.
    It wouldn't surprise me if there is some new, cheap vendor of wireless access points that doesn't do the network settings correctly and only Windows machines will connect to it.
    You were a ThinkPad owner, so you weren't a typical PC user anyway. Most of them use PCs only because they are cheap, cheap, cheap. Is it 3.29 cheaper than a Mac? Buy it! Those people are now making cheap wireless access turnkey solutions. I have seen people like that before. Just because there are hundreds of millions of pounds of equipment depending on the software, or people's lives, doesn't mean they know how to do networking. They may be so incompetent they don't know they are incompetent. Those types typcially would never, ever think to test their product on a Mac.

  • Unable to connect to internet as Self assigned IP address Since Aple repair

    Right this is currently winding me up a treat and i am posting this via windows under bootcamp on my iMac as it is the only way i can connect to the internet.
    Picked my iMac up from the Apple store in Bristol UK (i dont know if this is related or not) but the problem has only happened since the repair!
    I cannot connect to the internet or any services that use internet access, and under network settings, under ethernet it says connected (light in green) but you may be unable to access internet and it is self assigning IP address. If i go into advanced and renew DHCP nothing changes, its still has an IP address beginning 16 not 192. as normal.
    I have repaired permissions, reset the Pram restarted and nothing makes any difference! The router settings have not changed and are not at fault. i can access the internet from my Mac via bootcamp, or 2 other windows computers in the house and my iphone via wifi.
    Note my Mac wont connect via wireless either as it also self assigns IP address.
    I dont know what to try now and am getting fed up with this, as i never have problems that dont make sense with Macs i have been an avid user for 10 years, and am well clued up with them (normally).
    Can anyone shed anylight? Its a 2007 2.4Ghz Intel Core2Gb Ram 320Gb HDD 265Mb Radion HD Pro. Running OS 10.5.7 (not updated to 10.5.8 as came out when it was in for repair and i havent been able to access since)
    Thanks to anyone that can help!

    Right i have just rebooted after reading another post and under Security>Firewall>Allow all incoming connections this seems to allow me access (well currently so anyway)
    But surely this isnt right? IF i then go back to Set specific access its now ok, but i imagine it wont be if i rebooted with it like it was before.
    Also i notice i now have the follwing under allow access (which werent there before it went to the Apple store for repair)
    ntpd
    nmblookup
    krb5kdc
    I dont know what they are? Could it be this?
    Thanks

Maybe you are looking for