Recent content by Draggon

Update? I'm thinking of purchasing some Buffalo equipment and would like to hear your thoughts. Thanks!

Yeah, that's exactly what I've done. I put the Pre-N back into the system (not changing any client settings), reset it to factory defaults, changed only the items necessary to match my wireless settings (SSID, etc) and I get the same non-working system. As soon as I put the D-Link back, things...

Not quite. The success was not repeatable, and I still had major browsing issues between Desktop2 and Wireless1. As a further troubleshooting step, I disconnected the new Belkin Pre-N router and reconnected my old D-Link DI-614+. After configuring everything back to the defaults (DHCP...

That was the message at the command prompt. I don't know how to share in the command prompt environment, so I can't answer your question. Were you asking me to try "net use \\ip\Sharename" from the Start/Run menu instead? If so, I hadn't tried that before.

Just to try to eliminate one more thing that was bugging me, I powered down all three machines and switched the Router ports between Desktop1 and Desktop2 (D1 is now on Port 3 and D2 is now on Port 1). After rebooting, there is absolutely no change in symptoms. Desktop2 and Wireless1 simply...

Just basic file access between machines and sharing one printer. Yep, I've tried this, but the drive can't map, because Wireless1 just can't see Desktop2 no matter what I do (even with NetBEUI). Yeah, I've read many of the articles at ezlan.net over the last few days... :) As indicated...

Wireless1 to Desktop2: (after a looooong wait > 2 minutes) The command completed successfully. Wireless1 to Desktop1: (immediately) The command completed successfully. Desktop2 to Wireless1: (immediately) The command completed successfully. Desktop1 to Wireless1...

Thanks for the link, I'll read up on that. TCP/IP is the only protocol loaded on any of the three machines, and it's bound to both Client for Microsoft Networks and File and Printer Sharing in "Advanced Settings". Here ya go: DESKTOP1 IPCONFIG /ALL Windows IP Configuration...

That's not very encouraging, spidey... ;) On Wireless1, trying to access Desktop2, I get: System error 64 has occurred. The specified network name is no longer available. On Desktop2, trying to access Wireless1, I get: The command completed successfully.

I just checked the two Desktop machines. Both of them list the node as "Unknown", also. I've no idea how to enable broadcast or where to define the node. Yes, Router = .2.1 Desktop1 = .2.2 Desktop2 = .2.3 Wireless1 = .2.5 (.2.4 is a wireless laptop that I've taken out of the loop...

I will respectfully disagree, but only because I know more about what I've done to my systems than you do, and I agree that my post makes it sound like I've run willy-nilly through anything I could change. I'm an engineer by trade, so I'm very methodical in how I attack a problem. I start with...

Yeah, I kind of expected that one... :) First, thanks a lot for taking the time to respond. I'm on the verge of desperate here... IPCONFIG /ALL Windows IP Configuration Host Name . . . . . . . . . . . . : P-3 Primary Dns Suffix . . . . . . . : Node Type...

Typical home LAN setup: Desktop1 - Windows XP Pro SP2 - Connected to Port 1 of Router Desktop2 - Windows XP Pro SP2 - Connected to Port 3 of Router Wireless1 - Windows XP Pro SP2 - 802.11g Wireless Adapter (TrendNet) - Less than 15' from Router Signal Strength and Link Quality are both...

Just a thought, hanco, do you have the latest BIOS installed? What processor are you running on this board? 8K7A Latest Bios

Bump... No reply from EPOX yet either.... hmmmmmm.... Anyone? :)