224.0.0.1

  • Thread starter Thread starter Jim Carlock
  • Start date Start date
J

Jim Carlock

The DC keeps trying to connect to a 224.0.0.1 which seems
to be hardcoded into several dll files, including w32time.dll,
w32tm.exe and rsvp.exe. The IP address resolves to:
ALL-SYSTEMS.MCAST.NET

Those appear to be time files, but from what I'm reading, the
information that goes out is supposed to be router discovery
packets. I have blocked the outgoing requests in the firewall,
so all those packets are being dropped.

There's a registry key that indicates that it can be turned off
via these folks:

http://www.winguides.com/registry/display.php/581/

It seems to be a common issue for all operating systems these
days, and there are some posts about it on google found by
searching for:

all-systems.mcast.net

Curious about what you guys might have to say about this.
 
Just to add in and update my research on this:

A whois through geektools.com:

Checking server [whois.crsnic.net]
Checking server [whois.iana.org]
Results:
Domain mcast.net not found. Please note that this whois server only
provides information for a very few domains

It's the numbers 224.0.0.1 that are hard coded into the files listed.
Those numbers when I send information out to request a name
resolve to all-system.mcast.net.

Yet no one owns that domain name, yet it's registered on some
server somewhere.

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.


| The DC keeps trying to connect to a 224.0.0.1 which seems
| to be hardcoded into several dll files, including w32time.dll,
| w32tm.exe and rsvp.exe. The IP address resolves to:
| ALL-SYSTEMS.MCAST.NET
|
| Those appear to be time files, but from what I'm reading, the
| information that goes out is supposed to be router discovery
| packets. I have blocked the outgoing requests in the firewall,
| so all those packets are being dropped.
|
| There's a registry key that indicates that it can be turned off
| via these folks:
|
| http://www.winguides.com/registry/display.php/581/
|
| It seems to be a common issue for all operating systems these
| days, and there are some posts about it on google found by
| searching for:
|
| all-systems.mcast.net
|
| Curious about what you guys might have to say about this.
|
| --
| Jim Carlock
| http://www.microcosmotalk.com/
| Post replies to the newsgroup.
|
|
|
 
In
Jim Carlock said:
Just to add in and update my research on this:

A whois through geektools.com:

Checking server [whois.crsnic.net]
Checking server [whois.iana.org]
Results:
Domain mcast.net not found. Please note that this whois server only
provides information for a very few domains

It's the numbers 224.0.0.1 that are hard coded into the files listed.
Those numbers when I send information out to request a name
resolve to all-system.mcast.net.

Yet no one owns that domain name, yet it's registered on some
server somewhere.


Jim Carlock said:
The DC keeps trying to connect to a 224.0.0.1 which seems
to be hardcoded into several dll files, including w32time.dll,
w32tm.exe and rsvp.exe. The IP address resolves to:
ALL-SYSTEMS.MCAST.NET

Those appear to be time files, but from what I'm reading, the
information that goes out is supposed to be router discovery
packets. I have blocked the outgoing requests in the firewall,
so all those packets are being dropped.

There's a registry key that indicates that it can be turned off
via these folks:

http://www.winguides.com/registry/display.php/581/

It seems to be a common issue for all operating systems these
days, and there are some posts about it on google found by
searching for:

all-systems.mcast.net

Curious about what you guys might have to say about this.
Click to expand...
Click to expand...




Keep in mind Jim, this is a mutlicast IP address (Class D, 224.0.0.1 to
239.255.255.254) which is not an IP you would find on the Internet. I'm sure
you're famiar with what multicast is.

Not sure why it's doing this. Can't find much on the subject and watched
firewall logs with a few DCs and nothing of the sort is happening. One
friend mentioned it's the DC trying to listen to routing changes. Apparently
you can configure Windows to do this, but can't recall how... have to find
out. Or maybe it can come down to being a trojan or a hijack causing this.

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Ace mentioned:
| Keep in mind Jim, this is a mutlicast IP address (Class D, 224.0.0.1 to
| 239.255.255.254) which is not an IP you would find on the Internet. I'm
sure
| you're famiar with what multicast is.
|
| Not sure why it's doing this. Can't find much on the subject and watched
| firewall logs with a few DCs and nothing of the sort is happening. One
| friend mentioned it's the DC trying to listen to routing changes.
Apparently
| you can configure Windows to do this, but can't recall how... have to find
| out. Or maybe it can come down to being a trojan or a hijack causing this.
| --
| Regards,
| Ace

I guess it happens when the server is set up as a router/NAT.
But the actual address is stored inside of the w32 (time) files.

Okay, that answers why the address is not found on as a DNS
name on the Internic type places.

I had done a google search on it in the google groups... I
searched for the domain string I found.

ALL-SYSTEMS.MCAST.NET

is the actual line of text I searched for and found some
information about it. I'm guessing that it's the router
discovery packets going out as the DC has NAT and
routing configured on it.

I didn't realize the address was a multicast address. I
just know I resolved the address to a specific device,
that has a specific name, so I'm thinking someone has
a system set up out there with the name listed above.

Thanks for the reply Ace. I turned off the outgoing packets
in the firewall. They are dropped now. I still have some kind
of problem with FTP on an XP system. I think I messed up
the registry on that system, in some way. Everything works
on it except FTP and I can't get the Internet Firewall stuff
working on it. Has me baffled. <g>

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.


:
| Jim Carlock posted their thoughts, then I offered mine:
| > Just to add in and update my research on this:
| >
| > A whois through geektools.com:
| >
| > Checking server [whois.crsnic.net]
| > Checking server [whois.iana.org]
| > Results:
| > Domain mcast.net not found. Please note that this whois server only
| > provides information for a very few domains
| >
| > It's the numbers 224.0.0.1 that are hard coded into the files listed.
| > Those numbers when I send information out to request a name
| > resolve to all-system.mcast.net.
| >
| > Yet no one owns that domain name, yet it's registered on some
| > server somewhere.
| >
| > | >> The DC keeps trying to connect to a 224.0.0.1 which seems
| >> to be hardcoded into several dll files, including w32time.dll,
| >> w32tm.exe and rsvp.exe. The IP address resolves to:
| >> ALL-SYSTEMS.MCAST.NET
| >>
| >> Those appear to be time files, but from what I'm reading, the
| >> information that goes out is supposed to be router discovery
| >> packets. I have blocked the outgoing requests in the firewall,
| >> so all those packets are being dropped.
| >>
| >> There's a registry key that indicates that it can be turned off
| >> via these folks:
| >>
| >> http://www.winguides.com/registry/display.php/581/
| >>
| >> It seems to be a common issue for all operating systems these
| >> days, and there are some posts about it on google found by
| >> searching for:
| >>
| >> all-systems.mcast.net
| >>
| >> Curious about what you guys might have to say about this.
| >>
| >> --
| >> Jim Carlock
| >> http://www.microcosmotalk.com/
| >> Post replies to the newsgroup.

| Please direct all replies to the newsgroup so all can benefit.
| This posting is provided "AS IS" with no warranties.
|
| Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
| Microsoft Windows MVP - Active Directory
| --
| =================================
|
|
 
In
Jim Carlock said:
Ace mentioned:

I guess it happens when the server is set up as a router/NAT.
But the actual address is stored inside of the w32 (time) files.

Okay, that answers why the address is not found on as a DNS
name on the Internic type places.

I had done a google search on it in the google groups... I
searched for the domain string I found.

ALL-SYSTEMS.MCAST.NET

is the actual line of text I searched for and found some
information about it. I'm guessing that it's the router
discovery packets going out as the DC has NAT and
routing configured on it.

I didn't realize the address was a multicast address. I
just know I resolved the address to a specific device,
that has a specific name, so I'm thinking someone has
a system set up out there with the name listed above.

Thanks for the reply Ace. I turned off the outgoing packets
in the firewall. They are dropped now. I still have some kind
of problem with FTP on an XP system. I think I messed up
the registry on that system, in some way. Everything works
on it except FTP and I can't get the Internet Firewall stuff
working on it. Has me baffled. <g>
Click to expand...

On top of that, like to show you this article. It shows that address is also
a system discovery:
http://www.iana.org/assignments/multicast-addresses

I don't understand why it's broadcasting that. That's not normal. Is there
anything else configured in RRAS or any other software (like Ghost) that
supports mutlicast installed and running as a service on this machine?

As for the XP FTP issue, go into add/remove, and remove FTP, restart, then
reinstall it. See if that works.
Do you have a backup of this machine? Did you look into system restore for
XP?



--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Reinstall FTP? FTP is a protocol of TCPIP. TCPIP can NOT be
removed from XP machines. I've tried to remove TCP/IP by adding
NetBios thinking that it needed another protocol to be able to
remove TCP/IP, but TCP/IP can NOT be removed. At least not in
the standard way that I've remove TCP/IP in the past.

I'm not sure what you meant by the "remove FTP", but I'll take it
that you meant "remove TCP/IP". <g>

There are no backups. Or maybe there are so many backups that
I don't have a clue on where to begin. The system crashed due to
a failing hard drive in December and upon reinstalling XP, things
have never been the same. It's almost like it had bug free software
on it from a couple years ago, and all the new updates Microsoft
provides now seem to problematic. I only wish I had the software
I had on it 4 months ago. I'm just throwing darts at thin air there
but three months of reinstalling XP and nothing but various
problems has left in a dead end. <g> I think I might have actually
caused this problem though, because there were some keys in the
registry that I couldn't gain access to, and I ended up changing all
the policies on all the keys. No telling what's up with that.

I've been looking for information about the Windows Registry on
Win2K and XP machines, and I've seen what Microsoft is offering,
but I'm digging deeper, but I'm just so flabergasted by it all.

I need to take a step back and start doing this one step at a time.
So the FTP issue is first on the list now.

Funny thing about Windows 2k on up, is that these OS'es seem to
be writing information to files by going over the network. It's almost
like you need a network card on a machine to install the OS. That
brings up a question you might be able to answer. Have you ever
installed Win2K on a machine with no network adapter? I think
I'm going to pull out an old computer and take out the network
card and try it.

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.


"Ace Fekay [MVP]"
message | In | Jim Carlock <[email protected]> posted their thoughts, then I offered
mine
| > Ace mentioned:
| >> Keep in mind Jim, this is a mutlicast IP address (Class D, 224.0.0.1
| >> to 239.255.255.254) which is not an IP you would find on the
| >> Internet. I'm sure you're famiar with what multicast is.
| >>
| >> Not sure why it's doing this. Can't find much on the subject and
| >> watched firewall logs with a few DCs and nothing of the sort is
| >> happening. One friend mentioned it's the DC trying to listen to
| >> routing changes. Apparently you can configure Windows to do this,
| >> but can't recall how... have to find out. Or maybe it can come down
| >> to being a trojan or a hijack causing this. --
| >> Regards,
| >> Ace
| >
| > I guess it happens when the server is set up as a router/NAT.
| > But the actual address is stored inside of the w32 (time) files.
| >
| > Okay, that answers why the address is not found on as a DNS
| > name on the Internic type places.
| >
| > I had done a google search on it in the google groups... I
| > searched for the domain string I found.
| >
| > ALL-SYSTEMS.MCAST.NET
| >
| > is the actual line of text I searched for and found some
| > information about it. I'm guessing that it's the router
| > discovery packets going out as the DC has NAT and
| > routing configured on it.
| >
| > I didn't realize the address was a multicast address. I
| > just know I resolved the address to a specific device,
| > that has a specific name, so I'm thinking someone has
| > a system set up out there with the name listed above.
| >
| > Thanks for the reply Ace. I turned off the outgoing packets
| > in the firewall. They are dropped now. I still have some kind
| > of problem with FTP on an XP system. I think I messed up
| > the registry on that system, in some way. Everything works
| > on it except FTP and I can't get the Internet Firewall stuff
| > working on it. Has me baffled. <g>
| >
| >
|
| On top of that, like to show you this article. It shows that address is
also
| a system discovery:
| http://www.iana.org/assignments/multicast-addresses
|
| I don't understand why it's broadcasting that. That's not normal. Is there
| anything else configured in RRAS or any other software (like Ghost) that
| supports mutlicast installed and running as a service on this machine?
|
| As for the XP FTP issue, go into add/remove, and remove FTP, restart, then
| reinstall it. See if that works.
| Do you have a backup of this machine? Did you look into system restore for
| XP?
|
|
|
| --
| Regards,
| Ace
|
| Please direct all replies to the newsgroup so all can benefit.
| This posting is provided "AS IS" with no warranties.
|
| Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
| Microsoft Windows MVP - Active Directory
| --
| =================================
|
|
 
Jim Carlock said:
Reinstall FTP? FTP is a protocol of TCPIP. TCPIP can NOT be
removed from XP machines. I've tried to remove TCP/IP by adding
NetBios thinking that it needed another protocol to be able to
remove TCP/IP, but TCP/IP can NOT be removed. At least not in
the standard way that I've remove TCP/IP in the past.

I'm not sure what you meant by the "remove FTP", but I'll take it
that you meant "remove TCP/IP". <g>

There are no backups. Or maybe there are so many backups that
I don't have a clue on where to begin. The system crashed due to
a failing hard drive in December and upon reinstalling XP, things
have never been the same. It's almost like it had bug free software
on it from a couple years ago, and all the new updates Microsoft
provides now seem to problematic. I only wish I had the software
I had on it 4 months ago. I'm just throwing darts at thin air there
but three months of reinstalling XP and nothing but various
problems has left in a dead end. <g> I think I might have actually
caused this problem though, because there were some keys in the
registry that I couldn't gain access to, and I ended up changing all
the policies on all the keys. No telling what's up with that.

I've been looking for information about the Windows Registry on
Win2K and XP machines, and I've seen what Microsoft is offering,
but I'm digging deeper, but I'm just so flabergasted by it all.

I need to take a step back and start doing this one step at a time.
So the FTP issue is first on the list now.

Funny thing about Windows 2k on up, is that these OS'es seem to
be writing information to files by going over the network. It's almost
like you need a network card on a machine to install the OS. That
brings up a question you might be able to answer. Have you ever
installed Win2K on a machine with no network adapter? I think
I'm going to pull out an old computer and take out the network
card and try it.

--
Click to expand...

Jim,

You said you were having a problem with FTP, not TCP/IP, hence why I
answered such. FTP can be removed in Add/REmove, WIndows COmponents, etc.

To remove and reinstall TCP/IP, I can't find the one for XP, but this is
pretty much the same:
285034 - How to Remove and Reinstall TCPip for Windows 2000:
http://support.microsoft.com/default.aspx?scid=kb;en-us;285034

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Read inline...

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.


:
| "Jim Carlock" wrote:
| > Reinstall FTP? FTP is a protocol of TCPIP. TCPIP can NOT be
| > removed from XP machines. I've tried to remove TCP/IP by adding
| > NetBios thinking that it needed another protocol to be able to
| > remove TCP/IP, but TCP/IP can NOT be removed. At least not in
| > the standard way that I've remove TCP/IP in the past.
| >
| > I'm not sure what you meant by the "remove FTP", but I'll take it
| > that you meant "remove TCP/IP". <g>
|
| You said you were having a problem with FTP, not TCP/IP, hence why I
| answered such. FTP can be removed in Add/REmove, WIndows COmponents, etc.

Oh, Yeah, I've Uninstalled everything and the funny thing, XP doesn't
allow anyone to uninstall TCP/IP. I went through the Add/Remove
Programs (Windows Components) and removed all TCPIP networking,
removed all IIS... Took all the check marks out there for any networking
stuff. In fact, there is no FTP listed there. I'm still confused about what
you're talking about in that respect. If you think about it, FTP is a
protocol for connecting, transmitting and receiving over a specific port,
and it's a TCPIP protocol. Every protocol except TCPIP works on this
machine. And one other comment I'll add. I've seen questions in the XP
newsgroup that TCPIP cannot be uninstalled. And I can't do it from the
Network Properties. I can take the check mark out of it so it isn't used
but there is absolutely no way that I can see to "remove" TCPIP. All I
can do is put a check mark in the checkbox in the TCPIP properties
box or take the check mark out. Uninstall never enables itself.

The really funny thing is, that the domain is up and running and the
router is routing out to the internet, and I can connect to the domain
controller. I can read files off the Domain Controller. But I'm not joined
to the Domain.

How do I know I'm not joined? <g>

NetDiag reports:
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Failed
'HQ': No DCs are up.

Yet I can read everything on the domain controller. And I can log into
the domain controller, even though I'm not joined.

IPConfig reports:

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : hq.microcosmotalk.com
Description . . . . . . . . . . . : Linksys
Physical Address. . . . . . . . . : 00-00-00-00-00-00
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.10.1.4
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Default Gateway . . . . . . . . . : 10.10.1.1
DHCP Server . . . . . . . . . . . : 10.10.1.1
DNS Servers . . . . . . . . . . . : 10.10.1.1
Primary WINS Server . . . . . . . : 10.10.1.1
NetBIOS over Tcpip. . . . . . . . : Disabled
Lease Obtained. . . . . . . . . . : Thursday, March 11, 2004 7:29:57
PM
Lease Expires . . . . . . . . . . : Thursday, March 11, 2004
10:29:57 PM

The item you listed below doesn't work. That was one of the first
things I tried. I just don't see any way to UNINSTALL TCPIP.

I was thinking along the lines that reinstalling a Service Pack would
work but Microsoft made a service pack for XP work in the
following manner:

1) Act like you're installing things.
2) Report service pack installed successfully.

And when you go to look at what was installed, the new files that
were supposed to be replaced are still on the hard drive. The
time/date stamps and version numbers indicate that nothing was
installed.

Pinging myself works fine. Tracert works fine. HTTP, SMTP,
POP3 all work fine.

C:\Program Files\Support Tools>ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

I can tracert out to anything and get replies back. TCPIP
works 100% true to it's nature. It's just FTP that's not
working. Uninstalling and reinstalling TCPIP with full
reboots between each operation does nothing at all. DHCP
and DNS are working 100% great.

Hmmm, I wonder... maybe it's an Internet Explorer setting...

Bahh! I had to put a check mark into the Advanced Settings
of Internet Explorer for Use Passive FTP (for firewall and DSL
modem compatibility).

Yeesh.

I still have some other problem though whereby I cannot turn on the
Firewall deal for XP. I'll deal with that tomorrow. Thanks Ace!

Oh, keep in mind the link below doesn't apply to XP. TCPIP can not
be reinstalled or uninstalled. If you happen to find someone that knows
how to do it, send a message back to this newsgroup here. Thanks!

| To remove and reinstall TCP/IP, I can't find the one for XP, but this
| is pretty much the same:
| 285034 - How to Remove and Reinstall TCPip for Windows 2000:
| http://support.microsoft.com/default.aspx?scid=kb;en-us;285034
|
| --
| Regards,
| Ace
|
| Please direct all replies to the newsgroup so all can benefit.
| This posting is provided "AS IS" with no warranties.
|
| Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
| Microsoft Windows MVP - Active Directory
| --
| =================================
|
|
 
In
Jim Carlock said:
Read inline...




Oh, Yeah, I've Uninstalled everything and the funny thing, XP doesn't
allow anyone to uninstall TCP/IP. I went through the Add/Remove
Programs (Windows Components) and removed all TCPIP networking,
removed all IIS... Took all the check marks out there for any
networking stuff. In fact, there is no FTP listed there. I'm still
confused about what you're talking about in that respect. If you
think about it, FTP is a protocol for connecting, transmitting and
receiving over a specific port, and it's a TCPIP protocol. Every
protocol except TCPIP works on this machine. And one other comment
I'll add. I've seen questions in the XP newsgroup that TCPIP cannot
be uninstalled. And I can't do it from the Network Properties. I can
take the check mark out of it so it isn't used but there is
absolutely no way that I can see to "remove" TCPIP. All I
can do is put a check mark in the checkbox in the TCPIP properties
box or take the check mark out. Uninstall never enables itself.

The really funny thing is, that the domain is up and running and the
router is routing out to the internet, and I can connect to the domain
controller. I can read files off the Domain Controller. But I'm not
joined to the Domain.

How do I know I'm not joined? <g>

NetDiag reports:
DC discovery test. . . . . . . . . : Passed
DC list test . . . . . . . . . . . : Failed
'HQ': No DCs are up.

Yet I can read everything on the domain controller. And I can log into
the domain controller, even though I'm not joined.

IPConfig reports:

Ethernet adapter Local Area Connection:
Connection-specific DNS Suffix . : hq.microcosmotalk.com
Description . . . . . . . . . . . : Linksys
Physical Address. . . . . . . . . : 00-00-00-00-00-00
Dhcp Enabled. . . . . . . . . . . : Yes
Autoconfiguration Enabled . . . . : Yes
IP Address. . . . . . . . . . . . : 10.10.1.4
Subnet Mask . . . . . . . . . . . : 255.255.255.248
Default Gateway . . . . . . . . . : 10.10.1.1
DHCP Server . . . . . . . . . . . : 10.10.1.1
DNS Servers . . . . . . . . . . . : 10.10.1.1
Primary WINS Server . . . . . . . : 10.10.1.1
NetBIOS over Tcpip. . . . . . . . : Disabled
Lease Obtained. . . . . . . . . . : Thursday, March 11, 2004
7:29:57 PM
Lease Expires . . . . . . . . . . : Thursday, March 11, 2004
10:29:57 PM

The item you listed below doesn't work. That was one of the first
things I tried. I just don't see any way to UNINSTALL TCPIP.

I was thinking along the lines that reinstalling a Service Pack would
work but Microsoft made a service pack for XP work in the
following manner:

1) Act like you're installing things.
2) Report service pack installed successfully.

And when you go to look at what was installed, the new files that
were supposed to be replaced are still on the hard drive. The
time/date stamps and version numbers indicate that nothing was
installed.

Pinging myself works fine. Tracert works fine. HTTP, SMTP,
POP3 all work fine.

C:\Program Files\Support Tools>ping 127.0.0.1
Pinging 127.0.0.1 with 32 bytes of data:
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Reply from 127.0.0.1: bytes=32 time<1ms TTL=128
Ping statistics for 127.0.0.1:
Packets: Sent = 4, Received = 4, Lost = 0 (0% loss),
Approximate round trip times in milli-seconds:
Minimum = 0ms, Maximum = 0ms, Average = 0ms

I can tracert out to anything and get replies back. TCPIP
works 100% true to it's nature. It's just FTP that's not
working. Uninstalling and reinstalling TCPIP with full
reboots between each operation does nothing at all. DHCP
and DNS are working 100% great.

Hmmm, I wonder... maybe it's an Internet Explorer setting...

Bahh! I had to put a check mark into the Advanced Settings
of Internet Explorer for Use Passive FTP (for firewall and DSL
modem compatibility).

Yeesh.

I still have some other problem though whereby I cannot turn on the
Firewall deal for XP. I'll deal with that tomorrow. Thanks Ace!

Oh, keep in mind the link below doesn't apply to XP. TCPIP can not
be reinstalled or uninstalled. If you happen to find someone that
knows
how to do it, send a message back to this newsgroup here. Thanks!
Click to expand...





You know what Jim, it maybe easier just to throw the CDROM in and upgrade to
itself so it refreshes the installation, and then re-run the service pack.
There's seems to be alot going on with this machine, and it got corrupted
somehow. There is a way to yank out TCP/IP, and I saw a reference to it in
the past, but I cannot find it. Maybe as I said, the easiest and cleanest
fix it to just put the cd in and run an upgrade on top of the existing
system so you don;t lose any apps or personal settings.




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Finally found a link that explains how to reset TCP/IP on XP.
You might want to add it to your favorites just in case someone
else asks about it. I'm going to set it up on my website so I know
exactly how to get to it.

http://support.microsoft.com/?kbid=299357

Found the link by searching Google for:
XP reinstall TCPIP

I think my previous search bombed out because I was putting in
TCP/IP.

That Passive FTP has to be checked off in the Internet Explorer
settings to get the FTP to work. The rest of the problems I have
are partly because I'm not really logged into the domain, and the
computer is signing on to itself. But I can see the domain and I
can see the other systems on the domain when I go into browse
it. That is raising some other questions about how secure the
domain is.

I'll deal with those later. Have some other things I need to finish
up now.
 
In
Jim Carlock said:
Finally found a link that explains how to reset TCP/IP on XP.
You might want to add it to your favorites just in case someone
else asks about it. I'm going to set it up on my website so I know
exactly how to get to it.

http://support.microsoft.com/?kbid=299357

Found the link by searching Google for:
XP reinstall TCPIP

I think my previous search bombed out because I was putting in
TCP/IP.

That Passive FTP has to be checked off in the Internet Explorer
settings to get the FTP to work. The rest of the problems I have
are partly because I'm not really logged into the domain, and the
computer is signing on to itself. But I can see the domain and I
can see the other systems on the domain when I go into browse
it. That is raising some other questions about how secure the
domain is.

I'll deal with those later. Have some other things I need to finish
up now.
Click to expand...

Jim,
Thanks for the TCPIP link and glad you were able to find it.

As for FTP.....Passive in IE????? NOw I don't understand, I must have
totally miusunderstood your previous posts and your problems.

I thought you had a problem with XP's FTP service on the machine and you
were using it as an FTP server. I had no idea from what you were saying that
you were trying to connect to someone else's FTP service. ANd here I was
trying to help show you how to reinstall the FTP service, which has nothing
to do with connecting to an FTP site using IE. You didn't mention you were
trying to connect to an FTP site using IE. Here's from your original...
.... I still have some kind
of problem with FTP on an XP system. I think I messed up
the registry on that system, in some way. Everything works
on it except FTP and I can't get the Internet Firewall stuff
working on it. Has me baffled.
Click to expand...

From the above passage, it sounds like you'r ehaving trouble using the FTP
service on XP, not trying to connect to an FTP site using IE. Sorry, we need
to be a little more descriptive, or I may have to ask some more questions in
the future


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
LOL Sorry. I was so wrapped up in it and other things, and I kept
thinking I'm missing something simple. And I wasn't paying too
much attention to what I was posting. I kinda reached my wits end
in addressing this particular problem. And when I found I couldn't
uninstall and reinstall TCPIP in a simple fashion, I went over the
edge. <vbg>

--
Jim Carlock
http://www.microcosmotalk.com/
Post replies to the newsgroup.

- Never say never in the room,
- Except in the case of assumption,
- Never assume.

:
| Jim,
| Thanks for the TCPIP link and glad you were able to find it.
|
| As for FTP.....Passive in IE????? NOw I don't understand, I must have
| totally miusunderstood your previous posts and your problems.
|
| I thought you had a problem with XP's FTP service on the machine and you
| were using it as an FTP server. I had no idea from what you were saying
that
| you were trying to connect to someone else's FTP service. ANd here I was
| trying to help show you how to reinstall the FTP service, which has
nothing
| to do with connecting to an FTP site using IE. You didn't mention you were
| trying to connect to an FTP site using IE. Here's from your original...
|
| > .... I still have some kind
| > of problem with FTP on an XP system. I think I messed up
| > the registry on that system, in some way. Everything works
| > on it except FTP and I can't get the Internet Firewall stuff
| > working on it. Has me baffled.
|
| From the above passage, it sounds like you'r ehaving trouble using the FTP
| service on XP, not trying to connect to an FTP site using IE. Sorry, we
need
| to be a little more descriptive, or I may have to ask some more questions
in
| the future
| --
| Regards,
| Ace
 
In
Jim Carlock said:
LOL Sorry. I was so wrapped up in it and other things, and I kept
thinking I'm missing something simple. And I wasn't paying too
much attention to what I was posting. I kinda reached my wits end
in addressing this particular problem. And when I found I couldn't
uninstall and reinstall TCPIP in a simple fashion, I went over the
edge. <vbg>
Click to expand...

LOL, hey Jim, can I suggest some decaf?

Or even better, a beer and a shot of Crown Royal!

Cheers!
:-)


--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
In
Jim Carlock said:
I've been looking for information about patents and copyrights
lately, as well as information about the history of IBM and DOS.

Guess what!

http://www.igeek.com/articles/History/IsBillGatesAGenius.txt

Gotta love some of the stuff out there!
Click to expand...

Interesting article!

--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS IS" with no warranties.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Ace and anyone else, could I get a favor?

Could you do a search through a Windows\System32 or (system, if on
Win9x) for (Containing text:) 224.0.0.1 and could you relay what turns
up?

I'm getting the following files showing up on Win2K Advanced Server
machine:

c:\winnt\sytem32\w32tm.exe
c:\winnt\sytem32\w32time.dll
c:\winnt\sytem32\rsvp.exe

Nothing is showing up an XP machine. It does show up on a
Windows Me machine:

c:\windows\system\rsvp.exe

I was thinking it's related to a routing service on the server.
The server is trying to use WinLogon.exe to go out to
224.0.0.1 and I'm thinking it's originating at the XP machine,
as the XP machine is NOT actually logged onto the network.
It is but it isn't, and the server doesn't think it is and it knows
it isn't, but it's getting it's IP address, DHCP and such from
the domain controller.

When I was reading about the 015 service, I initially was looking
at it by going into the properties for the network adapter and
looking to see if there was a check mark in the network adapter
for the LAN. There isn't. The 015 service though is listed inside
of DHCP and is being used there to do what it does. I was
looking at the server that is handling the routing, DHCP, WINS
and DNS. It has two adapters on it. One adapter is used for
IIS to provide webpages.

I didn't see 015 listed anywhere within the network adapter
properties, so I was a little confused about what was going
on in Kevin's statements, but I think it's starting to make
sense now, and the only thing that I might be missing is the
check mark in the TCP/IP Advanced Properties/DNS tab.

I'm assuming now that the check mark there, for:

Use this connection's DNS suffix in DNS registration

is 015??? <g> Should that be checked on the network
card that is handing out DNS, DHCP, Nat/Routing for
the LAN?
 
In
Jim Carlock said:
Ace and anyone else, could I get a favor?

Could you do a search through a Windows\System32 or (system, if on
Win9x) for (Containing text:) 224.0.0.1 and could you relay what turns
up?

I'm getting the following files showing up on Win2K Advanced Server
machine:

c:\winnt\sytem32\w32tm.exe
c:\winnt\sytem32\w32time.dll
c:\winnt\sytem32\rsvp.exe

Nothing is showing up an XP machine. It does show up on a
Windows Me machine:

c:\windows\system\rsvp.exe

I was thinking it's related to a routing service on the server.
The server is trying to use WinLogon.exe to go out to
224.0.0.1 and I'm thinking it's originating at the XP machine,
as the XP machine is NOT actually logged onto the network.
It is but it isn't, and the server doesn't think it is and it knows
it isn't, but it's getting it's IP address, DHCP and such from
the domain controller.

When I was reading about the 015 service, I initially was looking
at it by going into the properties for the network adapter and
looking to see if there was a check mark in the network adapter
for the LAN. There isn't. The 015 service though is listed inside
of DHCP and is being used there to do what it does. I was
looking at the server that is handling the routing, DHCP, WINS
and DNS. It has two adapters on it. One adapter is used for
IIS to provide webpages.

I didn't see 015 listed anywhere within the network adapter
properties, so I was a little confused about what was going
on in Kevin's statements, but I think it's starting to make
sense now, and the only thing that I might be missing is the
check mark in the TCP/IP Advanced Properties/DNS tab.

I'm assuming now that the check mark there, for:

Use this connection's DNS suffix in DNS registration

is 015??? <g> Should that be checked on the network
card that is handing out DNS, DHCP, Nat/Routing for
the LAN?
Click to expand...

Option 015 sets the connection-specific DNS suffix and not necessarily the
Primary DNS Suffix for the machine.
http://support.microsoft.com/default.aspx?scid=kb;en-us;314822

And here's a repost that I found from a conversation between Kevin and I for
a poster:
http://www.webservertalk.com/message104026.html

So just keep the checkmark checked in IP properties, as well in Computer
Name properties in System Properties.


As for the 224.0.0.1, I found these on a W2k Pro machine:

c:\winnt\system32\hpdmip.hpa
c:\winnt\system32\rsvp.exe
c:\winnt\system32\w32time.dll
c:\winnt\system32\w32tm.exe




--
Regards,
Ace

Please direct all replies to the newsgroup so all can benefit.
This posting is provided "AS-IS" with no warranties and confers no
rights.

Ace Fekay, MCSE 2000, MCSE+I, MCSA, MCT, MVP
Microsoft Windows MVP - Active Directory
 
Back
Top