Advertisement
Okay, some of you may just laugh at me, but I'm completely at a loss and don't know where else to turn. My company manufactures glass tempering furnaces. I build and maintain the computers that control them. The OS is Windows XP Embedded, which I've been developing. I've gotten pretty good at it, except for a recent brick wall. We've got a furnace going into a facility in Billings, Montana that doesn't have a network. So, I've installed a good old dial-up modem (Diamond SM56LE 56k PCI PRO) and created it as a component in the XPe target image. Windows recognizes the device, loads the drivers, I create an "accept incoming connections" to set up the computer as a RAS server (I first had to install all the correct networking components in XPe, of course... whew) and it answers the phone and accepts the incoming user (the administrator account from my laptop) but then... *fizzle* nothing... It even stops recognizing the LAN (a Linksys 802.11g gateway/router) through the ethernet port. In order to get it back on the LAN I have to delete the "accept incoming connections" information, flush the DNS cache, release and renew the adapter and finally it starts networking again. I've also noticed that when it's connected to the remote computer it's own IP address and the Gateway IP are the same (which sounds correct because it's the RAS) but the subnet mask is 255.255.255.255??? Shouldn't that have a zero at the end? I can't ping the RAS from the remote computer, but I can ping the remote from the RAS, so the connection works one way but not the other.
I haven't diagnosed dial-up problems in, probably, five years. Where do I turn? The next thing I'm going to be trying is replacing hardware, which I've already done on this machine (the mobo was bad... I couldn't get it to recognize anything on the ISA bus... yes, ISA, the analog I/O cards that control some furnace elements are very old industrial technology) and had to reinstall my target XPe image, five times, as a result.
Any ideas? I'll wait until you stop laughing.
Love and light, dear ones.
Rev
I haven't diagnosed dial-up problems in, probably, five years. Where do I turn? The next thing I'm going to be trying is replacing hardware, which I've already done on this machine (the mobo was bad... I couldn't get it to recognize anything on the ISA bus... yes, ISA, the analog I/O cards that control some furnace elements are very old industrial technology) and had to reinstall my target XPe image, five times, as a result.
Any ideas? I'll wait until you stop laughing.
Love and light, dear ones.
Rev
posted by:
|
Portland
|
Advertisement
Advertisement
-
Re: Stinkin' dial-up...
Thu, March 15, 2007 - 7:54 AMFrom what I remember, when using RAS you need to have the RAS ID and network ID on different subnets, and then use ROUTE to get everything talking to each other.
Unfortunately, I'm a bit rusty with RAS, and don't have the information at the top of my head. And now, duty calls with one my clients having an "emergency", so I will have to leave with just the small bit of info above. Hopefully that's enough to start you off in the right direction, and it may possibly lead to an "ah ha!" moment. -
-
Re: Stinkin' dial-up...
Thu, March 15, 2007 - 10:23 PMThe network at the RAS XPe box needs to be a different subnet than the office you are connecting through or you just end up confusing it.
So if you are using 192.168.0.x (default on most gateways) for your local home network and 192.168.0.x on the network where the machine you are connecting from is dialing in from, you are going to run into lots of issues. Each office/network needs to be on a sepperate net. 192.168.1.x for main, 192.168.2.x for suboffice 1, etc...
I havent used RAS on XP in years, though I did recently reconfigure dial-up RAS on a Win2k server (dont ask) the other day and it worked just fine and allowed access to the network for the remote user (once you tell it they can access other resources). The IP address you are seeing is correct. When establishing a RAS connection you will see 255.255.255.255 mask because its limiting you to that one address. Its by design, even though it flys against everything we think about routing. Its simply saying this dial-up connection is limited to one point of connection.
So as Jason pointed out, make sure you arent using the default or same ip subnets at both locations. -
-
Re: Stinkin' dial-up...
Sat, March 24, 2007 - 6:39 AMSorry, I guess that I should tell you guys what the resolution was on this.
I hadn't completely added Internet Information Systems Technologies (IIS) and also had to add the graphical user interface (GUI) for the Windows Firewall Control Panel. Then, I had to manually set an exception for Printer & File Sharing. That allowed me to connect through the dial-up modem and view and change files. Harumph. It was Service Pack 2 stuff all along...
The client had their "computer consultant" call me yesterday morning to inform me that they have an ethernet network with a domain.
There's a moral to this story, I just know it. <sigh>
Love and light, dear ones.
Rev
-
-
