![]() |
Thank you SpaceBass.
I am in no hurry, so when you have time. fyi I can't go to softphone yet, as it is a different service according to my provider and it means having to pay all over again :rolleyes: |
So I have been playing around and tried to follow the instructions to set up a bridge connection.
I get stalled when Windows tells me I need 2 internet connections to build a bridge. Am I doing something wrong or is this not the bridge connection you meant? |
Originally Posted by MapleLeaf
(Post 6919070)
So I have been playing around and tried to follow the instructions to set up a bridge connection.
I get stalled when Windows tells me I need 2 internet connections to build a bridge. Am I doing something wrong or is this not the bridge connection you meant? |
Ok so if I follow you then I need to just make a bridge between my ethernet port and my wireless port?
I tried that and it set up a bridge but disconnected my wireless connection. It said the wireless was active but disconnected (if that makes sense). In order to post this, I had to remove the network bridge. Sigh! Sometimes this stuf is just too complicated. |
Sorry, you've exceeded my knowledge of Windows networking. I think your life will be much simpler if you purchase a bridge. Unfortunately, there may be some wrinkles. Do you have access to the building's router, or can you ask the admin to make a change? If so, get one of these, and give it a static IP. Add that IP address to the router's DMZ. Plug the voip box into the bridge and you're done.
If you don't have access to the building's router, I think you may have a problem. I've given it some more thought, and I now believe that without DMZ or port forwarding, I'm not sure any bridge is going to work. Sorry if I've led you astray. Have you asked your voip provider? Odds are, they don't support your net configuration, but if it's a small company you may find someone willing to help. |
Sorry its taken me so long... been one of the worst work weeks in a long time...
As others have suggested, there is a good chance, even with a laptop bridge, that you'll run into NAT issues. IF you have the option to use VPN on the laptop, that may be your saving grace. To make the bridge, right click on your wireless network connection and go to properties. Select 3rd tab (dont have XP in front of me, sorry) and select the internet connection sharing checkbox. There is a drop-down right below that where you pick a 'private network adaptor', thats where you select the network card that your IP phone will plug into, should be 'local area connection' most likely. Click ok, let XP do its thing... Now you have to configure the NAT settings for ICS (internet connection sharing). Go back into the advanced tab on the wireless adaptor, click the settings button in the ICS area. You'll need to add mappings for what ever ports that IP phone needs. If its running standard SIP those are UDP port 5060 and UDP ports 10000 - 20000 . You may need to contact your VoIP provider to find out what it needs specifically. Now, remember, thats only opening ports b/t the wireless signal and the hard-wired LAN adaptor. That does nothing regarding the NAT b/t the wireless network and the outside world....that may still be a problem, depending on how your VoIP provider has things setup. At this point you should be able to plug a cable b/t the phone and the laptop. The phone adaptor should get an IP like 192.168.1.100 (I think)... Again, you are at the mercy of the NAT b/t the wirelss network and the outside world.... If you have access to a VPN solution outside of the wireless network, you maybe able to do some more trickery. For instance, with the built in XP VPN client you can also share that connection via ICS. Follow the same process as above but use the VPN connection rather then the wireless adaptor. I think the cisco client allows that as well (but it can be turned off by the network admin). Finally, you could also use an SSH tunnel to another box...but thats just getting nerdy. All in all, my guess is the true limiting factor is going to be the NAT b/t the wireless network and the outside world. Some VoIP providers are doing symetrical SIP, where they use the same outgoing and incoming ports...some use something called STUN...both are ways of traversing NAT firewalls. If your VoIP provider is using either, then chances are the straight laptop bridge will work for you. Otherwise, you may be up a proverbial creek. If all else fails, look into http://www.jajah.com/ and Skype. You could always forward your existing VoIP number to something like Skype (which traverses firewalls very nicely). Jajah is slick...it baiscally lets you start calls via the web. So you put in your cell phone number (for example) and the number of who you want to call... it calls your cellphone first, you answer and then it calls the other party and merges the 2 calls...so both people recieve incoming calls and its all connected via VoIP...and its cheap! |
There is no drop down box when I activate ICS to pick private network adaptor.
Something tells me I am just F*d. The VoIP company suggested using a router as a bridge, set it up in client mode and let it receive the wireless signal and transmit it to the VoIP box. Been trying that for 2 days as well... Cable into the router from the laptop BUT when I enter the 192.168.0.XX address given to me by the router documentation, I never get the page to load, but do get a connection. Until I get that page to load, I can't program in the settings for the network so it can receive the signal. This is frustrating beyond belief. |
Originally Posted by MapleLeaf
(Post 6949367)
There is no drop down box when I activate ICS to pick private network adaptor.
Something tells me I am just F*d. The VoIP company suggested using a router as a bridge, set it up in client mode and let it receive the wireless signal and transmit it to the VoIP box. Been trying that for 2 days as well... Cable into the router from the laptop BUT when I enter the 192.168.0.XX address given to me by the router documentation, I never get the page to load, but do get a connection. Until I get that page to load, I can't program in the settings for the network so it can receive the signal. This is frustrating beyond belief. Type "cmd". Press enter. You should be in the command prompt. Type "ipconfig". Press enter. You should have an IP address next to "Default Gateway" (There might be more than one). Try that IP address in the browser instead of the one you used. This should take you to the router configuration. SmilingBoy. |
Originally Posted by MapleLeaf
(Post 6949367)
This is frustrating beyond belief. Really, and I hate to say this, I think even if you get a bridge working you'll have NAT issues. I think you should seriously look into other options. I'm not a skype fan personally, but skype with a usb handset may be your best option. Its cheap, it traverses firewalls well (assuming they aren't actively blocking it) and it just works. Froward your existing VoIP number to the skype number, or see if they'll do a 'hunt group' for you... You might even put some pressure on them to refund you since you cannot use it.... |
Originally Posted by SmilingBoy
(Post 6949389)
GYou should have an IP address next to "Default Gateway" (There might be more than one).
|
Originally Posted by MapleLeaf
(Post 6949586)
Isn't that the Default Gateway for the wireless connection? I would need to cable into the router that I am using as a bridge, the d-link router that will hook up to the VoIP box that will receive the wireless signal, independant of the wireless connection going into my laptop.
The trick is plugging the router into the computer too. The computer has to get an IP address from the router via DHCP, most likely you'll get 192.168.1.100 or something and the router (default gateway for the LAN connection) will become 192.168.1.1 Then you can open a browser and go to http://192.168.1.1 ... may need to disable wifi if they are using the same address scheme (and if thats the case you'll need to change the router to another bogon like 172.... or 10...). Does that D-link specifically support bridging (client mode)? |
Originally Posted by SpaceBass
(Post 6949628)
You are both right...
The trick is plugging the router into the computer too. The computer has to get an IP address from the router via DHCP, most likely you'll get 192.168.1.100 or something and the router (default gateway for the LAN connection) will become 192.168.1.1 Then you can open a browser and go to http://192.168.1.1 ... may need to disable wifi if they are using the same address scheme (and if thats the case you'll need to change the router to another bogon like 172.... or 10...). Does that D-link specifically support bridging (client mode)? I know this is a huge imposition on you SpaceBass, but would it be easier for you (and me) if I called you and we spent 5 minutes trying to do this via phone? haha, of course I will have to call on my mobile... |
Originally Posted by MapleLeaf
(Post 6949723)
I do get 192.168.1.100 as the DHCP.
To make sure not to confuse anything. Disable your wireless. Connect your computer and the router. Wait 10-20 seconds (you should get a message that the Local Area Connection is connected). Now follow the steps I set out above. Write down the IP address of your default gateway. Put this in the browser. You should be taken to the admin page. Configure as needed. SmilingBoy. |
ok tried to connect the router to the laptop with the wi-fi disabled... it comes back saying limited connectivity; it never acquires a network address.
Entering 192.167.0.104, the IP address for the wireless connection did nothing; same with entering 192.168.1.1, the default gateway for the wireless connection. Should I be assigning an IP address for the LAN connection? i.e. one of these so it makes the connection? Apparently my router has a default address of 192.168.0.30, but as I said before, that did nothing for me either. :( |
Oh, fer crying out loud! Why didn't someone just post the simple answer?
http://www.amazon.com/Linksys-WGA54G.../dp/B00009X6DT |
| All times are GMT -6. The time now is 1:18 am. |
This site is owned, operated, and maintained by MH Sub I, LLC dba Internet Brands. Copyright © 2026 MH Sub I, LLC dba Internet Brands. All rights reserved. Designated trademarks are the property of their respective owners.