From: Patrick W. <pa...@im...> - 2004-06-10 19:49:13
|
On Thursday 10 June 2004 04:07 am, ch...@to... wrote: > bridging does not work with wireless... > If by NAT you mean the crippled NAT called ICS that MS provides maby your > problem is two lans that are the same network. Lots of wireless routers > default to the 192.168.0.0/24 network and ICS also uses 192.168.0.0/24 > this is the only option in win2k FYI, it can also be changed in Win2k SP4.. after you enable it and let ICS= =20 slam the IP for that adapter to 192... I might have had to reboot or=20 disable/enable the adapter or something before it started working. Of=20 course, this was with two physical adapters, not one physical and the TAP=20 one. So try that if changing the wireless is harder or impractical. later, patbob > but I think it may be possible to change > it in XP after windows sets up ICS with the default. On 2k you must change > the default network on the wireless router. (It may be possible to use the > routing and remote access service but I think you need tools from the 2k > server cd to configure it) > > I've been unsuccessful in getting the network working with either > > the bridge or nat methods. Am using the Debian image. > > > > I got a little further with NAT but I suspect my routes were incorrect > > because of my wireless router. > > > > My question is, is the "Routing and Remote Access" service needed under > > win2k ? I hope not because that enables netbios. I couldn't find any > > requirements list on the Wiki site. |