Brando569
MemberContent Type
Profiles
Forums
Events
Everything posted by Brando569
-
I have 4 devices (3 bluetooth and 1 IR) that work perfectly in Linux/Android but either won't show at all or work horribly in Windows, and all devices say they work in Windows (they have windows specific keys). I have a cheap IR (or is it RF?) touchpad/keyboard combo that will work for about 10 minutes in Windows then will repeat the last pressed key multiple times, and the mouse will become choppy. I have a full-sized keyboard with an integrated trackpad that has 2 bluetooth radios and it drops out almost instantly after it connects to Windows, key presses lag by as much as 60 seconds and the trackpad lags horribly, but it works perfectly in Android, in fact I'm using it to type up this post. I just purchased another trackpad/mini keyboard combo (that was recommended by Lew from Unbox Therapy, IS11-BT05) and the freaking bluetooth adapter in Windows (which is integrated into my brand new Intel Skylake motherboard) doesn't detect it at all, yet it finds my roommates Roku 2 and my Nexus 6. I enabled search mode on the keyboard and enabled it on my Google Pixel C and it literally shows up in about a second and paired about 2 seconds after that with no password. The final device is actually the Dolphin Bar so I can use Wiimotes with the Dolphin (Wii) emulator, but that may be a problem with the knock-off remotes. To make it even more odd, I have been using wireless Logitech mice for about a decade and never had any issues, but then again those are most likely RF. There's no reason why these devices shouldn't work perfectly in Windows. I've also tried a USB bluetooth adapter and it isn't any better. Why is the Windows bluetooth stack such garbage? This one reason why I switched to Linux years ago and pretty much everything I own runs Linux, except for my Gaming/HTPC PC (the one I'm talking about in this post).
-
Thanks for the info Cluberti, I'll look into setting static routes then! Edit: I looked up how to do it and the process is simple but the idea behind it is confusing me. Using this page as a reference, should I define a route from the internal domain (10.66.160.xxx) to the external network (10.1.10.xxx) or vice versa? I'm trying to understand how this works since I'm a novice when it comes to routing and I have no idea how the routing tables for our network are setup since there are multiple domains and they span the entire USA. The only things I would like outside access for are web browsing and SSH (to my home computer) I need internal access for internal websites, remote desktop connections and SMB shares.
-
My bad , I should have said "reset" TCP/IP: http://support.microsoft.com/default.aspx?scid=kb;en-us;299357 jaclaz Thanks for the info, a TCP/IP stack reset seemed to fix the problem. I'm surprised that I never had to use that before, you learn something new every day The only problem now is that name resolution within the domain seems to be a little slow, but hell it's better than having to keep switching interfaces! Edit: I didn't really work actually, some pages were unblocked while others were still blocked :-/ As soon as I disabled the inside line, everything was accessible so it seems that it's still getting confused. @Allen2 thanks for the concern but keep ethical issues out of here considering it doesn't help answer the problem at all and just clogs up the thread. Also I can use the "outside line" whenever I would like, I just have to walk into our MDF and connect it. This solution just saves me a few minutes of time whenever I need to access something outside of our network.
-
@uid0 A VM wouldn't be ideal, it would just be easier to stick with my current solution of disabling one interface when I need access to the other. @jaclaz I could try that. How would I go about removing and reinstalling the TCP/IP stack, in the 15 years of using Windows I've never once done that. That tool may be useful also but probably not considering the that IPs are different subnets depending on the which interface it is. @Tripredacus Even though I've met him and talk to him occasionally, I'm pretty sure he wouldn't be too fond of this, neither would my boss. So a static IP is out of the question, I don't understand how this would help with DN resolution though. Are you confusing DHCP (serves out IP address) with DNS (correlates domain names to IP addresses)? I actually just installed Arch Linux on one of the boxes here in my office (since I'm a Linux guy first and foremost, and my boss said that I could do it) and I know it would be easier to do in Linux but I've hit a roadblock since my domain admin account doesn't have the privileges to add computers to domains so I'm waiting on seeing if I can do that :-/
-
I'm the IT guy at my job and I have dual NICs in my Dell 755. One NIC is connected to my company's corporate domain and is used to access internal sites and the file server (10.160.xx.xx subnet) and the other NIC is used to connect to the corporate network but bypasses the firewall/filtering software (10.1.xx.xx subnet). I'm using a program called ForceBindIP so that I can make specific programs use specific interfaces. The problem that I'm having is that when both interfaces are enabled Windows seems to get confused as to which DNS to use for which interface. Everything worked fine for a day or so until my co-worker disconnected one of my lines because other people in the office needed it, when I reconnected my line this problem started happening. If both interfaces are enabled and have the correct IP addresses, web browsing on both browsers linked to their respective interfaces doesn't work because it says that it can't resolve domain names to IP addresses, yet if you use IP addresses everything works fine. As soon as one interface is disabled, everything works fine once again. The NICs are assigned the proper DNS addresses (domain NIC uses the doman's DNS server, the outside NIC uses Comcast's DNS). I've tried reboots and ipconfig release and renew and it doesn't seem to fix the problem. Any other ideas?
-
I'm on a computer running Windows XP with PowerShell installed and I would like to be able to grab the IP address from the output of ipconfig, then place it into a variable that will be used as an argument when executing a program. I use Linux on my home computers, so I would know how to do it with shell scripting, but PowerShell is completely different (it reminds me of Java). I've gotten as far as storing the output of ipconfig in a variable but I don't know how to "grep" it out of all the ouput since I'm not good with RegEx and then store that string into a variable which will be called upon later. C:\Documents and Settings\bran>ipconfig Windows IP Configuration Ethernet adapter Local Area Connection: Connection-specific DNS Suffix . : domain.net IP Address. . . . . . . . . . . . : 10.6.16.2 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 10.6.16.1 Ethernet adapter Local Area Connection 2: Connection-specific DNS Suffix . : IP Address. . . . . . . . . . . . : 192.168.42.24 Subnet Mask . . . . . . . . . . . : 255.255.255.0 Default Gateway . . . . . . . . . : 192.168.42.129 The IP address that I would like to be able to grab is that of Ethernet adapter Local Area Connection 2, the first three octets are always the same (192.168.42) it is only the last octet that changes. So in short I would like something along the lines of this: $ip=ipconfig echo $ip [grab IP address and store it in a variable] forcebindip $ipaddress c:\program.exe or for those of you that understand shell scripting ipconfig | grep "192.168.42"| head -n1| cut -c 30 > $ip forcebindip $ip c:\program.exe
-
I actually forgot to install SP1, thanks for the reminder. I'll let you know if it still exists after.
-
First off I do realize that this topic is over a year old but I just wanted to follow up and say that my problem still stands and it isn't related to hardware. It is a problem with Windows 7. I just did a complete overhaul on my system and switched the processor from an AMD Athlon x2 6400 to an Intel Core i7 950, switched the ram from 2GB of DDR2 to 8GB of DDR3, switched the motherboard from a Gigabyte GA-MA790GP-UD4H to an MSI Big Bang Xpower, and upgraded to power supply from a 400 watt Enermax Liberty to a 750 watt Silverstone. I also did a clean install of Windows 7 Home Pro 64 bit. Granted I didn't change the videocard this time but previously when I was testing this initially I did test this out using both my onboard ATI chip and my add-in nVidia 8600 GTS. My friend also recently built a brand new computer with a Sandybridge based Core i7 and he said he had the same problem (before I ever mentioned it to him).